> Sure, If any build error, please send to mailing list/me first, as it maybe not the issue of gbs.
Hi Quang, Thanks for looking into this. I'm going to give you my exact commands, why I gave them, and the errors I'm receiving back as a result. # Verify that I have an ssh config file with host tizen % cat ~/.ssh/config Host tizen Hostname review.tizen.org IdentityFile ~/.ssh/id_rsa User smaurer Port 29418 # Make a pristine nchmod 644 ~/git2/.gbs.confew directory structure % mkdir ~/git2 % mv ~/GBS-ROOT ~/GBS-ROOT-SAVE % cd ~/git2 # Load the repository. Twice specifying to load only ivi.xml. Note I use the "tizen:" alias for review.tizen.org. It is the same. % repo init -u tizen:/scm/manifest -b tizen -m ivi.xml % repo sync -m ivi.xml # Edit .gbs.conf in the local directory as the instructions in https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build say to do: % chmod 644 .gbs.conf % vi .gbs.conf % cat .gbs.conf [general] tmpdir=/var/tmp/ profile = profile.tizen3.0 editor = vim packaging_branch = tizen work_dir=. user = smaurer passwdx = <redacted> [obs.tizen] url = https://api.tizen.org [repo.tizen3.0_x86] url=${work_dir}/pre-built/toolchain-x86/ [repo.tizen3.0_ivi] url=http://download.tizen.org/snapshots/tizen/ivi/ [profile.tizen3.0] obs = obs.tizen repos=repo.tizen3.0_x86,repo.tizen3.0_ivi buildconf=${work_dir}/scm/meta/build-config/build.conf # Start the initial build to break cyclic dependencies (again, as the instructions state) % gbs build -A i586 --threads=4 --clean-once --exclude=gcc,cmake,filesystem,aul,libmm-sound,libtool > build1.out # The first gbs build fails largely because of a missing package: glibc-locale % tail build1.out python-magic: nothing provides python-devel nothing provides zlib-devel nothing provides glibc-locale autoconf: nothing provides glibc-locale cpio: nothing provides glibc-locale # Start the subsequent build % gbs build -A i586 --threads=4 --binary-list=gcc,cmake,filesystem,aul,libmm-sound,libtool --exclude=gettext,eglibc,curl,setup,privacy-manager-server,avsystem,texinfo > build2.out # The subsequent build doesn't magically provide the missing glibc-locale package (unlikely but had to check) % tail build2.out nothing provides pkgconfig(zlib) nothing provides procps nothing provides glibc-locale libtool: nothing provides zlib-devel nothing provides makeinfo nothing provides glibc-locale ...and there is where I am. I believe I've followed the instructions perfectly. But glibc-local is missing from the ivi.xml manifest. Any aid in either fixing the build or correcting something I've done wrong would be appreciated. Steve Maurer On 28 August 2013 03:13, Zhang, Qiang Z <[email protected]> wrote: > Sure, If any build error, please send to mailing list/me first, as it > maybe not the issue of gbs.**** > > ** ** > > Thanks**** > > Qiang**** > > ** ** > > ** ** > > *From:* VanCutsem, Geoffroy > *Sent:* Wednesday, August 28, 2013 6:04 PM > *To:* Zhang, Qiang Z; Hanchett, Paul; Steven Maurer > > *Cc:* [email protected] > *Subject:* RE: Building Tizen IVI 3.0 locally with gbs**** > > ** ** > > Hi Qiang,**** > > ** ** > > Thanks for this update, I much appreciate your reactivity!**** > > ** ** > > I’m going to try this out and report any issue in JIRA. Should these be > filed under ‘Development Tools’ -> ‘GBS’?**** > > ** ** > > Thanks,**** > > Geoffroy**** > > ** ** > > *From:* Zhang, Qiang Z > *Sent:* Wednesday, August 28, 2013 11:53 AM > *To:* VanCutsem, Geoffroy; Hanchett, Paul; Steven Maurer > *Cc:* [email protected] > *Subject:* RE: Building Tizen IVI 3.0 locally with gbs**** > > ** ** > > Hi Geoffroy,**** > > ** ** > > We have just finish updating manifest and document, major updates as > follows:**** > > ** ** > > - Document: add tizen 3.0 ivi/mobile profile build document, detail > command to sync code:**** > > $ repo init -u > ssh://<username>@review.tizen.org:29418/scm/manifest -b tizen -m ivi.xml**** > > * $ repo sync* > > * More details please see: > https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build > * > > *- Manifest updates:* > > *Add ivi/mobile support: add ivi.xml and mobile.xml* > > * * > > *With the above updates, please clone ivi code using above command, all > the ivi project will be synced to local.* > > * * > > * * > > *Thanks* > > *Qiang* > > * * > > ** ** > > ** ** > > *From:* [email protected] > [mailto:[email protected]<[email protected]>] > *On Behalf Of *VanCutsem, Geoffroy > *Sent:* Wednesday, August 28, 2013 5:10 PM > *To:* Hanchett, Paul; Steven Maurer > *Cc:* [email protected] > *Subject:* RE: Building Tizen IVI 3.0 locally with gbs**** > > ** ** > > 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]<[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.**** > -- Kind Regards Steven Maurer ------------------- 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 This e-mail and any attachments contain confidential information for a specific individual and purpose. The information is private and privileged and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, please e-mail us immediately. We apologise for any inconvenience caused but you are hereby notified that any disclosure, copying or distribution or the taking of any action in reliance on the information contained herein is strictly prohibited. This e-mail does not constitute an order for goods or services unless accompanied by an official purchase order.
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
