Hi Venkat, We have done some work to fix possible issue this week, here's some fixes:
1. wrt/libtapi issue: already fixed in today's release: http://download.tizen.org/releases/daily/tizen/ivi/latest/builddata/manifest/tizen_20130913.12_ia32.xml 2. update ivi toolchain to latest gcc48, which will fix some build error. 3. curl related bug. We also update pre-built/toolchain-x86 and scm/build-config based on latest released version, which also fix some possible build error. Thanks Qiang -----Original Message----- From: venkat [mailto:[email protected]] Sent: Friday, September 13, 2013 4:22 PM To: Ding, Jian-feng Cc: Zhang, Qiang Z; Hanchett, Paul; [email protected] Subject: Re: Building Tizen IVI 3.0 locally with gbs Hi Jian-feng, Any update on these package issues? When can I expect these fixes, so that I can do full local build? Regards, Venkat On Friday 06 September 2013 05:58 PM, Jian-feng Ding wrote: > Hi, Venkat > > It seems another package issue, for the frequently used broken > pakcages, we will help to fix it along with maintainers to speed up the > progress. > > thanks > - jf.ding > > On Fri, Sep 06, 2013 at 12:17:45PM +0530, venkat wrote: >> Hi Paul, >> >> With the "latest" version also, I am getting the same errors. Can >> anyone help me out to fix this? >> >> Regards, >> Venkat >> >> On Tuesday 03 September 2013 06:54 AM, Hanchett, Paul wrote: >> >> Hi Venkat-- >> >> From the errors you're seeing, I'd wonder if somehow the sources are >> not in >> sync with the build process. It looks to me like you've gotten a bit >> farther than we have so far... I'm away from the company computer, but I >> think that we've fallen back to using 'latest' vs 'snapshot' branches >> for >> our builds. >> >> Steve Maurer could tell you more, he's in the thick of it. >> >> Sorry that I don't have an answer for you. :-( >> >> Paul >> >> >> >> Paul Hanchett >> ------------------- >> Infotainment Engineer >> MSX on behalf of Jaguar Land Rover >> One World Trade Center, 121 Southwest Salmon Street, 11th Floor, >> Portland, >> Oregon, 97204 >> >> Email: [email protected] >> ------------------- >> >> Business Details: >> Jaguar Land Rover Limited >> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF >> Registered in England No: 1672070 >> >> >> On Mon, Sep 2, 2013 at 6:20 AM, venkat <[email protected]> wrote: >> >> Hi Geoffroy, >> >> While building 3.0 M2 packages, we are able to build most of the >> upstream packages except some. I have attached logs for libcap and >> smack packages. Can you please let me know what is the issue? >> >> We are using Ubuntu 12.04. >> >> Regards, >> Venkat >> >> >> On Thursday 29 August 2013 03:07 PM, VanCutsem, Geoffroy wrote: >> >> >> Hi Venkat, >> >> >> >> libtapi - Can I use the same tag (that exists in the manifest? >> >> [Geoffroy] Yes >> wrt - What should be the tag to be used? >> >> [Geoffroy] Replace the revision tag by this one: submit/tizen/ >> >> 20130716.222709-0-ga8cd04578ff0ff57ef5e1a8ad3c1c261df9a1d43 >> >> >> >> I ve also attached that very manifest file with the >> modifications >> in for your convenience. >> >> >> >> Thanks, >> >> Geoffroy >> >> >> >> From: venkat [mailto:[email protected]] >> Sent: Thursday, August 29, 2013 11:31 AM >> To: VanCutsem, Geoffroy >> Cc: [email protected] >> Subject: Re: Building Tizen IVI 3.0 locally with gbs >> >> >> >> Hi Geoffroy, >> >> I am using this manifest.xml >> http://download.tizen.org/releases/milestone/tizen/ivi/ >> tizen_20130729.2/images/ivi-release-mbr-i586/ >> tizen_20130729.2-ivi-release-mbr-i586.manifest.xml >> >> libtapi - Can I use the same tag (that exists in the manifest? >> wrt - What should be the tag to be used? >> >> On Thursday 29 August 2013 02:44 PM, VanCutsem, Geoffroy wrote: >> >> Hi Venkat, >> >> >> >> These are known issues which I have reported to our team >> already: >> >> - libslp-tapi: this package was recently renamed to libtapi >> but >> the manifest file has not yet been updated. I expect this >> to be >> done shortly and in the meantime you can manually change >> that >> in the manifest file. >> >> - wrt: some of the git history/previous commits got partly >> lost >> which means the repo tool can t find the original tag >> anymore. >> This will be fixed the next time there is a new commit made >> to >> this project. Are you using the latest manifest from scm/ >> manifest or a specific one (like I do below)? >> >> >> >> Geoffroy >> >> >> >> From: venkat [mailto:[email protected]] >> Sent: Thursday, August 29, 2013 9:00 AM >> To: [email protected] >> Cc: VanCutsem, Geoffroy >> Subject: Re: Building Tizen IVI 3.0 locally with gbs >> >> >> >> One more package can't be found "wrt". >> >> On Thursday 29 August 2013 12:07 PM, venkat wrote: >> >> Hi Geoffroy, >> >> We are able to sync all the repo packages except >> libslp-tapi. Can you let me know how to clone this >> (Tizen >> IVI 3.0 M2)? We are getting teh following error. >> >> fatal: Project not found: platform/core/telephony/ >> libslp-tapi >> fatal: The remote end hung up unexpectedly >> >> Regards, >> Venkat >> >> >> >> On Wednesday 28 August 2013 02:40 PM, VanCutsem, >> Geoffroy >> wrote: >> >> Hi Paul, >> >> >> >> The instructions on the wiki are a little too >> generic >> and we need to enhance these to also cover the use >> cases which are of interest to you, i.e. the >> ability to >> rebuild from sources a complete image locally using >> gbs, keeping in mind that that image will in most >> cases >> not be the very latest daily release. I ll put this >> on >> my To-Do list along with Tomasz feedback that a >> wiki >> page on how to create a package from scratch for >> Tizen >> IVI would be useful. >> >> >> >> Regarding the manifest files, there are still a few >> glitches in these, even in the one I ve pointed at >> below (i.e. the libslp-tapi and wrt packages failed >> to >> be cloned when I tried it our yesterday and if you >> look >> at the bottom of the manifest file you ll notice >> that >> it failed to understand where three of the packages >> came from). We ve only recently introduced these so >> it >> s not, as expected, perfect yet. You testing these >> is >> actually also very useful to highlight some of the >> gaps >> or problems that we may miss. >> >> >> >> Cheers, >> >> Geoffroy >> >> >> >> From: Hanchett, Paul [ >> mailto:[email protected]] >> Sent: Tuesday, August 27, 2013 7:12 PM >> To: VanCutsem, Geoffroy; Steven Maurer >> Cc: [email protected] >> Subject: Re: Building Tizen IVI 3.0 locally >> with gbs >> >> >> >> Geoffroy-- >> >> >> >> Hard to fault your logic; basically you're saying >> the >> instructions in the article have gotten stale and >> need >> to be updated for the present project set-- Right? >> >> >> >> Paul >> >> >> >> >> >> Paul Hanchett >> ------------------- >> Infotainment Engineer >> MSX on behalf of Jaguar Land Rover >> One World Trade Center, 121 Southwest Salmon Street, >> 11th Floor, Portland, Oregon, 97204 >> >> Email: [email protected] >> ------------------- >> >> Business Details: >> Jaguar Land Rover Limited >> Registered Office: Abbey Road, Whitley, Coventry CV3 >> 4LF >> >> Registered in England No: 1672070 >> >> >> >> On Tue, Aug 27, 2013 at 10:08 AM, VanCutsem, >> Geoffroy < >> [email protected]> wrote: >> >> Hi all, Paul, >> >> >> >> There were various threads about this topic but >> instead >> of replying to one I just decided to start (yet) a >> new >> one. >> >> >> >> I went through the wiki page that is used as a >> starting >> point for the exercise of trying to recompile Tizen >> IVI >> locally from sources using GBS: https:// >> source.tizen.org/documentation/developer-guide/ >> >> creating-tizen-platform-image-scratch-through-local-build >> >> >> >> Although I have not gone through the entire exercise >> myself yet, the very first thing that looked a >> little >> awkward to me is that the manifest file that is >> referenced (i.e. >> https://review.tizen.org/git/?p=scm/ >> >> manifest.git;a=tree;h=refs/heads/tizen;hb=refs/heads/ >> tizen) does not seem to match the list of packages >> that >> we actually use in Tizen IVI 3.0 there are >> packages in >> there that we do *not* use in IVI and also some >> others >> that we do but are not listed in there. I believe a >> better starting point may actually be to use the >> manifest file that gets published along with a >> particular image (and so you can also decide which >> image you want to rebuild from scratch). As an >> example, >> the manifest for the Tizen IVI 3.0-M2-Jul release >> can >> be found here: http://download.tizen.org/releases/ >> milestone/tizen/ivi/tizen_20130729.2/images/ >> ivi-release-mbr-i586/ >> >> tizen_20130729.2-ivi-release-mbr-i586.manifest.xml >> >> >> >> So I think at a minimum, we should use that file by >> copying it in the .repo/manifests folder and >> initialise >> the system using this: repo init m >> >> tizen_20130729.2-ivi-release-mbr-i586.manifest.xml >> >> >> >> Like I said, I haven t gone through the entire >> exercise >> yet but hopefully I will get around to try this out >> shortly and I will report back to the list if I have >> any more success. >> >> >> >> Cheers, >> >> Geoffroy >> >> >> >> Intel Corporation NV/SA >> Kings Square, Veldkant 31 >> 2550 Kontich >> RPM (Bruxelles) 0415.497.718. >> Citibank, Brussels, account 570/1031255/09 >> >> This e-mail and any attachments may contain >> confidential material for the sole use of the >> intended >> recipient(s). Any review or distribution by others >> is >> strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all >> copies. >> >> >> _______________________________________________ >> IVI mailing list >> [email protected] >> https://lists.tizen.org/listinfo/ivi >> >> >> >> Intel Corporation NV/SA >> Kings Square, Veldkant 31 >> 2550 Kontich >> RPM (Bruxelles) 0415.497.718. >> Citibank, Brussels, account 570/1031255/09 >> >> This e-mail and any attachments may contain >> confidential material for the sole use of the >> intended >> recipient(s). Any review or distribution by others >> is >> strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all >> copies. >> >> >> >> >> >> >> _______________________________________________ >> >> IVI mailing list >> >> [email protected] >> >> https://lists.tizen.org/listinfo/ivi >> >> >> >> >> -- >> >> Regards, >> >> Venkat >> >> >> >> >> -- >> >> Regards, >> >> Venkat >> >> >> >> >> -- >> >> Regards, >> >> Venkat >> >> Intel Corporation NV/SA >> Kings Square, Veldkant 31 >> 2550 Kontich >> RPM (Bruxelles) 0415.497.718. >> Citibank, Brussels, account 570/1031255/09 >> >> This e-mail and any attachments may contain confidential >> material for the sole use of the intended recipient(s). Any >> review or distribution by others is strictly prohibited. If >> you >> are not the intended recipient, please contact the sender >> and >> delete all copies. >> >> >> >> -- >> >> Regards, >> >> Venkat >> >> Intel Corporation NV/SA >> Kings Square, Veldkant 31 >> 2550 Kontich >> RPM (Bruxelles) 0415.497.718. >> Citibank, Brussels, account 570/1031255/09 >> >> This e-mail and any attachments may contain confidential >> material >> for the sole use of the intended recipient(s). Any review or >> distribution by others is strictly prohibited. If you are not >> the >> intended recipient, please contact the sender and delete all >> copies. >> >> >> -- >> Regards, >> Venkat >> >> >> _______________________________________________ >> IVI mailing list >> [email protected] >> https://lists.tizen.org/listinfo/ivi >> >> >> >> >> >> -- >> Regards, >> Venkat >> >> _______________________________________________ >> IVI mailing list >> [email protected] >> https://lists.tizen.org/listinfo/ivi > -- Regards, Venkat _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
