Hi, Jinil We are doing tizen_2.1 local full build testing tonight. We will give you more info tomorrow.
Thanks Junchun Guan > -----Original Message----- > From: IVI [mailto:[email protected]] On Behalf Of Jinil P. > Sent: Monday, August 11, 2014 5:45 PM > To: Lv, RuiX; Wang, Ning W; Graydon, Tracy; [email protected] > Cc: Anoop Babu > Subject: RE: Expansion errors during GBS build > > Dear Rui, > > A gentle reminder about the below mail. > Could you please help to resolve these expansion errors as we are blocked due > to this. > > Thanks & Regards > Jinil P > > ________________________________________ > From: Jinil P. > Sent: Thursday, August 07, 2014 7:40 PM > To: Lv, RuiX; Wang, Ning W; Graydon, Tracy; [email protected] > Cc: Anoop Babu > Subject: RE: Expansion errors during GBS build > > Dear Rui, > > Thank you for the reply. > I have followed the same procedure as mentioned in the below mail. > But the build was getting aborted showing expansion error for all the > packages. > I have attached the complete build log with this mail. > Could you help to resolve this issue please. > > Thank you for your support. > > Thanks & Regards > Jinil P > > ________________________________________ > From: Lv, RuiX [[email protected]] > Sent: Thursday, August 07, 2014 1:01 PM > To: Jinil P.; Wang, Ning W; Graydon, Tracy; [email protected] > Cc: Anoop Babu > Subject: RE: Expansion errors during GBS build > > Hi Jin, > > It's the build.conf that interferes with your GBS local full build. > > More specifically, > When initializing repo using `$ repo init -u tizen:scm/manifest -b tizen -m > ivi.xml`, the latest version of build.conf for Tizen 3.0 IVI on Tizen Gerrit > will be > synced to ${work_dir}/scm/meta/build-config/build.conf. > > However, to successfully build Tizen 2.0 IVI, you need to replace it with the > previous version located at > http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/. > > In your gbs.conf, > > you've already added this remote repo, as shown below: > " > [repo.tizen2.0_ivi] > url=http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/ > " > Then you forced GBS to use the latest build.conf (for Tizen 3.0) by specifying > `buildconf` as ${work_dir}/scm/meta/build-config/build.conf in > [profile.tizen2.0_ivi] section, as shown below: > " > [profile.tizen2.0_ivi] > repos=repo.tizen2.0_arm, repo.tizen2.0_ivi > buildconf=${work_dir}/scm/meta/build-config/build.conf > " > > Two methods to fix the build.conf issue: > > 1. Remove " buildconf=${work_dir}/scm/meta/build-config/build.conf " in > "[profile.tizen2.0_ivi]" section. > 2. Download the correct build.conf from > http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/builddata/ > and replace ${work_dir}/scm/meta/build-config/build.conf with it by running > the following command: > > wget > http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/builddata/f9 > f233a412203d0b2f7383b2bb4c7ae729ffe7f4ed1a6b0083673599550b50b2-build > .conf -O ${work_dir}/scm/meta/build-config/build.conf > > After getting the build.conf ready, run the following commands to retrigger > local full build: > > $ > accel_pkgs="bash,bzip2-libs,c-ares,cmake,coreutils,diffutils,eglibc,elfutils-lib > elf,elfutils-libs,elfutils,fdupes,file,findutils,gawk,gmp,gzip,libacl,libattr,libcap,lib > curl,libfile,libgcc,liblua,libstdc++,make,mpc,mpfr,ncurses-libs,nodejs,nspr,nss-s > oftokn-freebl,nss,openssl,patch,popt,rpm-build,rpm-libs,rpm,sed,sqlite,tar,xz-li > bs,zlib,binutils,gcc" > $ gbs build -A armv7l --threads=4 --clean-once > --exclude=${accel_pkgs},filesystem,aul,libmm-sound,libtool --clean-repos > > Note: "--clean-repos" must be added for the first time to make sure local > repo > does not contain any old rpms that may affect the build results. > > For details, please refer to > https://source.tizen.org/documentation/developer-guide/getting-started-guid > e/building-packages-locally-gbs > > Rui > > -----Original Message----- > From: IVI [mailto:[email protected]] On Behalf Of Wang, Ning W > Sent: Thursday, August 07, 2014 1:54 PM > To: Graydon, Tracy; [email protected] > Cc: Anoop Babu > Subject: RE: Expansion errors during GBS build > > Hi Tracy, > > Build.conf has been moved to new path: > http://download.tizen.org/snapshots/tizen/ivi/latest/repos/atom/packages/re > podata/ > > Thanks, > Ning > > -----Original Message----- > From: IVI [mailto:[email protected]] On Behalf Of Graydon, Tracy > Sent: Thursday, August 07, 2014 2:37 AM > To: [email protected] > Cc: Anoop Babu > Subject: Re: Expansion errors during GBS build > > It sounds like you might need a different build.conf. The full gbs build will > use > the build.con from the scm/meta repo. That is not necessarily the most recent, > or specific build.conf you would want. The project config that is in > scm/meta/build-config is dated. You might try using a more recent conf file, > such as this one: > http://download.tizen.org/releases/milestone/tizen/ivi/latest/builddata/9da42 > 5cfb71134f628f39486390ae2ce370e55cfdf73e2702821ebbaced9a630-build.con > f > > For some reason I am not seeing a published build.conf for our latest > milestone > release and our newer snapshots. I am not sure whether that is intentional or > not. > > If you use a newer build.conf and you still hit "have choice" errors, you can > modify your build.conf to "Prefer:" the package you want. If you are not sure > which package to chose in such cases, we can surely help you with that on this > list. > > Hope that helps resolve the issue for you. Let us know. :) > > Tracy > > From: "Jinil P." <[email protected]<mailto:[email protected]>> > Date: Wednesday, August 6, 2014 at 5:10 AM > To: "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>> > Cc: Anoop Babu > <[email protected]<mailto:[email protected]>> > Subject: Expansion errors during GBS build > > Hi, > > I am trying to build the rootfs for Tizen IVI. > Followed the below steps for GBS build > 1. Configured the ~/.ssh/config as shown below Host review.tizen.org > Hostname review.tizen.org Port 29418 User <INPUT_YOUR_USER> # > ProxyCommand connect -S <proxy:port> %h %p > > Host tizen > Hostname review.tizen.org > Port 29418 > User <INPUT_YOUR_USER> > # ProxyCommand connect -S <proxy:port> %h %p > > 2. Fetched the Tizen IVI source by following the below steps $ mkdir > ~/tizen_ivi_src & cd ~/tizen_ivi_src $ repo init -u tizen:scm/manifest -b > tizen -m > ivi.xml > > 2.1. Configured the > /home/sfm/TizenManualBuild/UsingIA32/tizen_ivi_src/.repo/manifests/ivi/pre > built.xml as below <?xml version="1.0" encoding="UTF-8"?> <manifest> > <project name="pre-built/toolchain-arm" path="pre-built/toolchain-arm" > groups="prebuilts" revision="tizen_2.1"/> </manifest> > > 2.2. $ wget > http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/buildda... > -O .repo/manifests/ivi/projects.xml $ sed -i > '3,4d' .repo/manifests/ivi/projects.xml $ repo sync -j 32 # sync code > > 3. Updated the ~/tizen_ivi_src/.gbs.conf as shown below [general] > tmpdir=/var/tmp/ profile = profile.tizen2.0_ivi work_dir=. > > [repo.tizen2.0_arm] > url=${work_dir}/pre-built/toolchain-arm/ > > # Newly added repo > [repo.tizen2.0_ivi] > url=http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/ > > [profile.tizen2.0_ivi] > repos=repo.tizen2.0_arm, repo.tizen2.0_ivi > buildconf=${work_dir}/scm/meta/build-config/build.conf > > 4. Executed the following command to build the packages $ nohup gbs build -A > armv7l --threads=4 --exclude=libtool,gettext,emulator-yagl >build.log 2>&1 > > But the build was getting aborted by showing the message "error: <gbs>some > packages failed to be built" > There were 882 expansion errors for a total of 882 packages. > > ---------------------------------------------------------------------------------------------------------------- > - > Few of the errors are listed below > > capi-content-mime-type: > have choice for libexpat.so.1 needed by cmake: libexpat expat have choice for > libgmp.so.10 needed by coreutils: libgmp gmp ... > ... > m4: > have choice for libgmp.so.10 needed by coreutils: libgmp gmp have choice for > glibc-devel needed by rpm-build: glibc-devel eglibc-devel ... > ... > ---------------------------------------------------------------------------------------------------------------- > - > > The complete build log is attached with this mail. > > Could anyone help to resolve these errors please. > > The above steps were taken from the link below > https://source.tizen.org/documentation/articles/creating-tizen-ivi-image... > > Thanks & Regards > Jinil P > > > ________________________________ > > Confidentiality Statement / Disclaimer : This message and any attachments is > intended for the sole use of the intended recipient. It may contain > confidential > information. Any unauthorized use, dissemination or modification is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately then delete it from all your systems, and do not copy, use or > print. > Internet communications are not secure and it is the responsibility of the > recipient to make sure that it is virus/malicious code exempt. > > The company/sender cannot be responsible for any unauthorized alterations or > modifications made to the contents. If you require any form of confirmation of > the contents, please contact the company/sender. The company/sender is not > liable for any errors or omissions in the content of this message. > > ________________________________ > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > ________________________________ > > Confidentiality Statement / Disclaimer : This message and any attachments is > intended for the sole use of the intended recipient. It may contain > confidential > information. Any unauthorized use, dissemination or modification is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately then delete it from all your systems, and do not copy, use or > print. > Internet communications are not secure and it is the responsibility of the > recipient to make sure that it is virus/malicious code exempt. > > The company/sender cannot be responsible for any unauthorized alterations or > modifications made to the contents. If you require any form of confirmation of > the contents, please contact the company/sender. The company/sender is not > liable for any errors or omissions in the content of this message. > > ________________________________ > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
