Hi Jinil I've modified a little in the attached document with red font, please follow it to do gbs build. If meet other issues, ask me.
Thanks Li Jinjing -----Original Message----- From: Jinil P. [mailto:jini...@nestgroup.net] Sent: Tuesday, August 26, 2014 9:45 PM To: Li, JinjingX; Lv, RuiX Cc: Anoop Babu; ivi@lists.tizen.org Subject: Re: Expansion error while GBS build Hi Li, Thanks for reply. Please find the attached document describing the steps which we are planning to do to build the tizen rootfs. Could you please verify whether it is correct or not. Thanks in Advance. Thanks & Regards Jinil P On Monday 25 August 2014 09:56 PM, Li, JinjingX wrote: > Hi Jinil > > Based on the build.log and .repo.cache you sent. What caused expansion error > "nothing provides libcurl.so.4(CURL_OPENSSL_3) needed by ecore-con " is local > repo has higher priority than remote repo you added in .gbs.conf, gbs chooses > the libcurl-7.28.1-2.1.armv7l.rpm from prebuilt/toolchain-arm by default, > this libcurl provides libcurl.so.4(CURL_OPENSSL_4) but not > libcurl.so.4(CURL_OPENSSL_3). So you should remove the local libcurl > packages, and add curl to --exclude packages queue. > > You could follow the next steps: > > First, remove the libcurl series packages, curl and cmake from dir > prebuilt/toolchain-arm, then create new repo. > $ pwd > tizen_source/prebuilt/toolchain-arm > $ rm -f libcurl* cmake -2.8.5-1.2.armv7l.rpm curl-7.28.1-2.1.armv7l.rpm > $ rm -rf repodata > $ createrepo . > > Second, remove the libcurl and curl series packages under buildroot, let gbs > get libcurl from remote repo. > $ pwd > ~/GBS-ROOT/local/repos/tizen3.0_ivi/armv7l/RPMS > $ rm -f libcurl* curl* > > Third, rebuilt the source code with the command: > $ gbs build -A armv7l --threads=4 --clean-once > --exclude=${accel_pkgs},filesystem,aul,libmm-sound,libtool ,curl > > > I have one question, according to your buildlog, there are 821 packages being > built, are you using manifest from > http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/builddata/manifest/tizen-2.0_20131119.2_armv7l.xml > ? > For example, the packages "capi-system-haptic" and "corewatcher" in > the manifest are commented out, but in your build.log they were built failed; > no packages "weston-ivi" and "gcc48" in the manifest, but they exist in your > build.log. > > There are less than 750 packages in the manifest above. > > Thanks > Li Jinjing > > > -----Original Message----- > From: IVI [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Jinil P. > Sent: Wednesday, August 20, 2014 6:55 PM > To: Zhang, Qiang Z; Lv, RuiX > Cc: Anoop Babu; ivi@lists.tizen.org > Subject: Re: Expansion error while GBS build > > On Thursday 14 August 2014 04:35 PM, Zhang, Qiang Z wrote: >> Yes, please. >> >> You can go through all of our discussion, and we emphasize that the >> importance of .gbs.conf, so if you are not familiar with gbs.conf, don't >> change it again and again. >> >> Thanks >> Qiang >> >> >> -----Original Message----- >> From: Jinil P. [mailto:jini...@nestgroup.net] >> Sent: Thursday, August 14, 2014 6:37 PM >> To: Zhang, Qiang Z; Lv, RuiX >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Dear QIang, >> >> Thank you for the reply. >> I shall do the below mentioned modifications and send you the .repo.cache >> and gbs build. >> >> Thanks & Regards >> Jinil P >> >> ________________________________________ >> From: Zhang, Qiang Z [qiang.z.zh...@intel.com] >> Sent: Thursday, August 14, 2014 3:21 PM >> To: Jinil P.; Lv, RuiX >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Hi Jinil, >> >> >> Your .gbs.conf is totally mess, please use the following .gbs.conf >> >> [general] >> tmpdir=/var/tmp/ >> profile=profile.tizen2.0_ivi >> work_dir=. >> >> [repo.tizen2.0_arm] >> url=/home/sfm/TizenManualBuild/UsingIA32/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 >> >> >> Then try again, and give your .repo.cache and gbs build output log. >> >> Thanks >> QIang >> >> >> >> -----Original Message----- >> From: Jinil P. [mailto:jini...@nestgroup.net] >> Sent: Thursday, August 14, 2014 5:40 PM >> To: Lv, RuiX; Zhang, Qiang Z >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Dear Rui, >> >> Thank you for the reply. >> >> Please find the details below. >> Conf files are attached with this mail. >> GBS build command used >> $ >> accel_pkgs="bash,bzip2-libs,c-ares,cmake,coreutils,diffutils,eglibc,elfutils-libelf,elfutils-libs,elfutils,fdupes,file,findutils,gawk,gmp,gzip,libacl,libattr,libcap,libcurl,libfile,libgcc,liblua,libstdc++,make,mpc,mpfr,ncurses-libs,nodejs,nspr,nss-softokn-freebl,nss,openssl,patch,popt,rpm-build,rpm-libs,rpm,sed,sqlite,tar,xz-libs,zlib,binutils,gcc" >> # For Devices image >> $ gbs build -A armv7l --threads=4 --clean-once >> --exclude=${accel_pkgs},filesystem,aul,libmm-sound,libtool >> -clean-repos >build.log 2>&1 >> >> Thanks & Regards >> Jinil P >> ________________________________________ >> From: Lv, RuiX [ruix...@intel.com] >> Sent: Thursday, August 14, 2014 2:23 PM >> To: Jinil P.; Zhang, Qiang Z >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Hi Jinil, >> >> After analyzing the build.log, >> we find that more than one repos are put to use during the building process, >> causing gbs have trouble making choice when two packages can be provided by >> both repos, thus displaying errors like the following: >> >> 140 have choice for ncurses needed by ncurses-libs: ncurses libncurses >> 141 have choice for libgmp.so.10 needed by gcc: libgmp gmp >> 142 have choice for libmpfr.so.4 needed by gcc: libmpfr mpfr >> >> Please send us the following materials for us to further analyze and provide >> practical solution for you: >> * ~/GBS-ROOT/local/order/.repo.cache >> * .gbs.conf >> * gbs build command >> >> Rui >> >> -----Original Message----- >> From: Jinil P. [mailto:jini...@nestgroup.net] >> Sent: Wednesday, August 13, 2014 7:25 PM >> To: Lv, RuiX; Zhang, Qiang Z >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Dear Rui, >> >> Thank you for the reply. >> >> After using the below mentioned manifest and toolchain I am getting >> expansion errors for all of the packages. >> manifest - >> http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/buil >> d >> data/manifest/ toolchain - >> https://review.tizen.org/gerrit/gitweb?p=pre-built%2Ftoolchain-arm.git;a=shortlog;h=refs%2Fheads%2Ftizen_2.1 >> ( The latest commit ). >> >> The build.log is attached with this mail. >> >> Please help to resolve these expansion errors. >> >> Thanks & Regards >> Jinil P >> ________________________________________ >> From: Lv, RuiX [ruix...@intel.com] >> Sent: Tuesday, August 12, 2014 7:31 PM >> To: Jinil P.; Zhang, Qiang Z >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Hi Jinil, >> >> To build tizen 2.0 ivi arm image, tizen_2.1 branch of toolchain-arm should >> be used. >> Tizen_ivi branch does not work, so please switch to tizen_2.1 branch of >> toolchain-arm. >> >> Rui >> >> -----Original Message----- >> From: Jinil P. [mailto:jini...@nestgroup.net] >> Sent: Tuesday, August 12, 2014 9:45 PM >> To: Zhang, Qiang Z; Lv, RuiX >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Dear Qiang, >> >> Thanks for the reply. >> >> Please see the output of command mentioned in below mail. >> ls >> /home/sfm/TizenManualBuild/UsingIA32/tizen_ivi_src/pre-built/toolchai >> n >> -arm/|grep x86-arm >> sfm@D0938-UBUNTU:~/TizenManualBuild/UsingIA32/tizen_ivi_src$ >> >> As you said I think *x86-arm packages are missing. >> Please let me know in which release of ARM toolchain these packages are >> available. >> >> Thanks & Regards >> Jinil P >> ________________________________________ >> From: Zhang, Qiang Z [qiang.z.zh...@intel.com] >> Sent: Tuesday, August 12, 2014 7:05 PM >> To: Jinil P.; Lv, RuiX >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Could you please show me the output of: >> >> $ ls >> /home/sfm/TizenManualBuild/UsingIA32/tizen_ivi_src/pre-built/toolchain-arm/|grep >> x86-arm ? >> >> >> From your original expansion error log, these *x86-arm packages are missing, >> but these packages should be exist in pre-built/toolchain-arm/ project. >> >> >> Thanks >> Qiang >> >> >> -----Original Message----- >> From: IVI [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Jinil P. >> Sent: Tuesday, August 12, 2014 9:21 PM >> To: Lv, RuiX >> Cc: ivi@lists.tizen.org; Anoop Babu >> Subject: RE: Expansion error while GBS build >> >> Dear Rui, >> >> Kindly ignore the below mail. >> >> I was trying to do the GBS build locally. >> The build.conf, .gbs.conf, prebuilt.xml and the output log generated are >> attached with this mail. >> The arm tool chain was downloaded from revision tizen_ivi. >> There were expansion errors for all 787 packages. >> Could you please help to resolve these errors. >> >> Thanks & Regards >> Jinil P >> ________________________________________ >> From: Jinil P. >> Sent: Tuesday, August 12, 2014 5:48 PM >> To: Lv, RuiX >> Cc: Anoop Babu; Li, JinjingX; Guan, JunchunX; Wang, Ning W; Graydon, >> Tracy; ivi@lists.tizen.org >> Subject: RE: Jinil's source >> >> Dear Rui, >> >> I was trying to do the GBS build locally. >> The build.conf, .gbs.conf and the output log generated are are attached with >> this mail. >> >> >> Thanks & Regards >> Jinil P >> ________________________________________ >> From: Lv, RuiX [ruix...@intel.com] >> Sent: Tuesday, August 12, 2014 1:02 PM >> To: Jinil P. >> Cc: Anoop Babu; Li, JinjingX; Guan, JunchunX; Wang, Ning W; Graydon, >> Tracy; ivi@lists.tizen.org >> Subject: Jinil's source >> >> ~/projects/tizen_2.x.src$ >> >> -----Original Message----- >> From: Lv, RuiX >> Sent: Tuesday, August 12, 2014 3:20 PM >> To: 'Jinil P.' >> Cc: Anoop Babu; Li, JinjingX; Guan, JunchunX; Wang, Ning W; Graydon, >> Tracy; ivi@lists.tizen.org >> Subject: RE: Expansion errors during GBS build >> >> Hi Jinil, >> >> Sorry for keeping you waiting. >> >> The expansion errors you reported the second time are different from the >> first batch. >> From the latest expansion error log, It's clear that pre-built/toolchain-arm >> local repo has not been put to use for gbs building. >> >> Please use the gbs.conf 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 repos=repo.tizen2.0_ivi >> >> Rui >> >> -----Original Message----- >> From: Jinil P. [mailto:jini...@nestgroup.net] >> Sent: Tuesday, August 12, 2014 1:06 PM >> To: Li, JinjingX; Guan, JunchunX; Lv, RuiX; Wang, Ning W; Graydon, >> Tracy; ivi@lists.tizen.org >> Cc: Anoop Babu >> Subject: RE: Expansion errors during GBS build >> >> Hi All, >> >> We are building for tizen 2.0 ivi. >> Tizen 2.0 IVI >> http://download.tizen.org/releases/previews/2.0/ivi-panda/latest/ >> >> We need to understand what is the cause of the expansion errors? How we can >> resolve these errors? >> >> Thanks & regards >> Jinil P >> >> -----Original Message----- >> From: Li, JinjingX [mailto:jinjingx...@intel.com] >> Sent: Monday, August 11, 2014 8:06 PM >> To: Jinil P. >> Cc: Anoop Babu; Guan, JunchunX; Lv, RuiX; Wang, Ning W; Graydon, >> Tracy; ivi@lists.tizen.org >> Subject: RE: Expansion errors during GBS build >> >> Hi, Jinil P >> >> What version of Tizen are you going to build, tizen2.2 or tizen3.0? >> >> About Tizen2.2, it doesn't distinguish profiles as IVI and Common, and we >> don't support tizen2.2 for long time. >> About Tizen 3.0, it has Tizen IVI and Tizen Common profiles, for tizen IVI, >> gbs build supports arch i586 now . >> >> Thanks >> Li Jinjing >> >> -----Original Message----- >> From: IVI [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Guan, >> JunchunX >> Sent: Monday, August 11, 2014 8:02 PM >> To: Jinil P.; Lv, RuiX; Wang, Ning W; Graydon, Tracy; >> ivi@lists.tizen.org >> Cc: Anoop Babu >> Subject: RE: Expansion errors during GBS build >> >> 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:ivi-boun...@lists.tizen.org] On Behalf Of Jinil P. >>> Sent: Monday, August 11, 2014 5:45 PM >>> To: Lv, RuiX; Wang, Ning W; Graydon, Tracy; ivi@lists.tizen.org >>> 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; ivi@lists.tizen.org >>> 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 [ruix...@intel.com] >>> Sent: Thursday, August 07, 2014 1:01 PM >>> To: Jinil P.; Wang, Ning W; Graydon, Tracy; ivi@lists.tizen.org >>> 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/bui >>> l d data/ 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/bui >>> l >>> d >>> data/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, >>> e >>> l >>> futils-lib >>> elf,elfutils-libs,elfutils,fdupes,file,findutils,gawk,gmp,gzip,libac >>> l >>> , >>> libattr,libcap,lib >>> curl,libfile,libgcc,liblua,libstdc++,make,mpc,mpfr,ncurses-libs,node >>> j >>> s >>> ,nspr,nss-s >>> oftokn-freebl,nss,openssl,patch,popt,rpm-build,rpm-libs,rpm,sed,sqli >>> t >>> e >>> ,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-start >>> e >>> d >>> -guid >>> e/building-packages-locally-gbs >>> >>> Rui >>> >>> -----Original Message----- >>> From: IVI [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Wang, >>> Ning W >>> Sent: Thursday, August 07, 2014 1:54 PM >>> To: Graydon, Tracy; ivi@lists.tizen.org >>> 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/pack >>> a >>> g >>> es/re >>> podata/ >>> >>> Thanks, >>> Ning >>> >>> -----Original Message----- >>> From: IVI [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Graydon, >>> Tracy >>> Sent: Thursday, August 07, 2014 2:37 AM >>> To: ivi@lists.tizen.org >>> 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/buildd >>> a >>> t >>> a/9da42 >>> 5cfb71134f628f39486390ae2ce370e55cfdf73e2702821ebbaced9a630-build.co >>> n >>> 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." >>> <jini...@nestgroup.net<mailto:jini...@nestgroup.net>> >>> Date: Wednesday, August 6, 2014 at 5:10 AM >>> To: "ivi@lists.tizen.org<mailto:ivi@lists.tizen.org>" >>> <ivi@lists.tizen.org<mailto:ivi@lists.tizen.org>> >>> Cc: Anoop Babu >>> <anoop.b...@nestgroup.net<mailto:anoop.b...@nestgroup.net>> >>> 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/i >>> v i /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 >>> IVI@lists.tizen.org >>> https://lists.tizen.org/listinfo/ivi >>> _______________________________________________ >>> IVI mailing list >>> IVI@lists.tizen.org >>> 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 >>> IVI@lists.tizen.org >>> https://lists.tizen.org/listinfo/ivi >> _______________________________________________ >> IVI mailing list >> IVI@lists.tizen.org >> 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. >> >> ________________________________ >> ________________________________ >> >> 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. >> >> ________________________________ >> ________________________________ >> >> 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. >> >> ________________________________ >> ________________________________ >> >> 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. >> >> ________________________________ >> ________________________________ >> >> 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. >> >> ________________________________ >> ________________________________ >> >> 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. >> >> ________________________________ >> > Dear Qiang, > > I had given GBS build with the modified GBS conf as per your earlier mail. > But there were lots of expansion errors. > The complete build log is attached with this mail. > Also I couldn't find the .repo.cache in my GBS roots and in source. > Could you please help to solve this issue. > > 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. > > ________________________________ > ________________________________ 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. ________________________________
Building the Tizen Rootfs.doc.odt
Description: Building the Tizen Rootfs.doc.odt
_______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
