Qiang,
My repo init and sync -m xxxxx seem to both be successful. However when I
try a gbs build, I get an error (two actually):
==================================================================================================
gbs build -A i586 --threads 2 --clean-repos --exclude=texinfo,systemd
==================================================================================================
info: generate repositories ...
warning: No such repo path:/home/paulha/20130913.12/pre-built/toolchain-x86/
error: Traceback (most recent call last):
File "/usr/bin/gbs", line 539, in <module>
sys.exit(main(sys.argv))
File "/usr/bin/gbs", line 533, in main
return module.main(args)
File "/usr/lib/pymodules/python2.7/gitbuildsys/cmd_build.py", line 290,
in main
cmd += prepare_repos_and_build_conf(args, buildarch, profile)
File "/usr/lib/pymodules/python2.7/gitbuildsys/cmd_build.py", line 140,
in prepare_repos_and_build_conf
shutil.copy(profile.buildconf, distconf)
File "/usr/lib/python2.7/shutil.py", line 119, in copy
copyfile(src, dst)
File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory:
'/home/paulha/20130913.12/scm/meta/build-config/build.conf'
My partner across the way is able to get past this. The one difference I
know about is that I am starting with a new set of directories where he is
re-using existing directory structures.
Do you think that's a clue?
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 Fri, Sep 13, 2013 at 3:57 AM, Zhang, Qiang Z <[email protected]>wrote:
> Hi Paul,****
>
> ** **
>
> I found new version of IVI is released:
> http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130913.12/****
>
> ** **
>
> In this release contains the following updates as I know:****
>
> - 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
> ****
>
> - Toolchain: use gcc48 instead of gcc 47, so gcc and toolchain conflict
> issue will be fixed.****
>
> - curl updated, so CURL_OPENSSL_4 related error will be fixed****
>
> ** **
>
> Gerrit git updates:****
>
> - Update scm/meta/build-conf to latest released config****
>
> - Update pre-built/toolchain-x86 to latest toolchain, including (gcc48,new
> eglibc)****
>
> ** **
>
> So with above updates, gbs local full build can works more better, only 28
> packages build failed.****
>
> ** **
>
> So, please build using latest code and repo:****
>
> ** **
>
> - use this manifest
> http://download.tizen.org/releases/daily/tizen/ivi/latest/builddata/manifest/tizen_20130913.12_ia32.xml
> to update
> scm/manifest/ivi-projects.xml<http://download.tizen.org/releases/daily/tizen/ivi/latest/builddata/manifest/tizen_20130913.12_ia32.xml%20to%20update%20scm/manifest/ivi-projects.xml>
> ****
>
> - use remote repo
> http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130913.12/ in
> .gbs.conf****
>
> - run gbs build --clean-repos****
>
> ** **
>
> Btw, latest tizen3.0 code does not exist package cycles , so you don’t
> need specify --exclude now.****
>
> ** **
>
> Thanks****
>
> Qiang****
>
> ** **
>
> ** **
>
> === the following packages failed to build due to missing build
> dependencies (*5) *===****
>
> cross-i386-gcc48-icecream-backend:****
>
> nothing provides cross-i386-binutils****
>
> gcc48-testresults:****
>
> nothing provides fastjar****
>
> nothing provides dejagnu****
>
> libgcj48:****
>
> nothing provides fastjar****
>
> syncevolution:****
>
> nothing provides libboost_thread.so.1.49.0 needed by libphonenumber****
>
> libwsbm:****
>
> nothing provides psb-headers****
>
> ** **
>
> === the following packages failed to build due to rpmbuild issue *(23*)
> ===****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> Thanks****
>
> Qiang****
>
> ** **
>
> *From:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Hanchett, Paul
> *Sent:* Friday, September 13, 2013 1:32 AM
>
> *To:* [email protected]
> *Subject:* (Re)Building the IVI M2 Aug release****
>
> ** **
>
> I am trying to recreate the IVI M2 Aug release, using the manifest file
> and process suggested by Geoffroy to us so we could get the same sources
> used for IVI M2 Aug:****
>
> ** **
>
> To do that, I created a new working directory. I got the manifest file,
> changed the name of libslp-tapi to libtapi (as suggested else where), and
> also commented out the project tag referencing "web/wrt". Then I copied the
> resulting manifest into
> .repo/manifests/tizen_20130829.9-ivi-release-mbr-i586.manifest.xml.****
>
> ** **
>
> I used this script to init and sync the work directory:****
>
> ** **
>
> #****
>
> # Initialize the repository to Tizen 3.0 IVI M2 Aug branch, warts and all.
> ****
>
> #****
>
> export USER="paulha"****
>
> ** **
>
> echo Initialize the repository to Tizen 3.0 IVI M2 Aug branch, warts and
> all.****
>
> echo repo init -u ssh://[email protected]/scm/manifest -m
> tizen_20130829.9-ivi-release-mbr-i586.manifest.xml****
>
> repo init -u ssh://[email protected]/scm/manifest -m
> tizen_20130829.9-ivi-release-mbr-i586.manifest.xml****
>
> echo repo sync****
>
> repo sync****
>
> ** **
>
> I put this .gbs.conf script into the working directory, with buildroot
> pointing at a new build root:****
>
> ** **
>
> [general]****
>
> tmpdir=/var/tmp/****
>
> # -- Use this profile as a default****
>
> profile = profile.tizen3.0****
>
> # -- 'tizen' is the Tizen 3.0 (ivi) branch****
>
> packaging_branch = tizen****
>
> editor = vim****
>
> work_dir=.****
>
> buildroot = ~/GBS-TIZEN-3.0M2****
>
> ** **
>
> ** **
>
> [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/releases/daily/tizen/ivi/latest/****
>
> ** **
>
> [profile.tizen3.0]****
>
> obs = obs.tizen****
>
> # refers back to earlier sections****
>
> repos=repo.tizen3.0_x86,repo.tizen3.0_ivi****
>
> buildconf=${work_dir}/scm/meta/build-config/build.conf****
>
> ** **
>
> Then I invoked my build script:****
>
> ** **
>
> echo
> ==================================================================================================
> ****
>
> echo gbs build -A i586 --threads 2 --clean-once
> --exclude=gcc,cmake,filesystem,aul,libmmsound,libtool,systemd****
>
> echo
> ==================================================================================================
> ****
>
> gbs build -A i586 --threads 2 --clean-once
> --exclude=gcc,cmake,filesystem,aul,libmmsound,libtool,systemd****
>
> echo DONE.****
>
> ** **
>
> Note that "systemd" has been added to the exclude list because an initial
> pass reported a circularity error systemd->dbus->systemd.****
>
> ** **
>
> I ended up with some 195 packages built, and around 70 with 5 classes of
> errors:****
>
> ** **
>
> *54 instances of Conflict between libstdc++ 4.7 and 4.8*****
>
> ** **
>
> Looks like this:****
>
> ** **
>
> [ 64s] [90/156] installing libstdc++-4.8.1-1.20****
>
> [ 64s] [91/156] installing libstdc++47-4.7.2-2.11****
>
> [ 64s] file /usr/lib/libstdc++.so.6 from install of
> libstdc++47-4.7.2-2.11.i686 conflicts with file from package
> libstdc++-4.8.1-1.20.i686****
>
> [ 64s] exit ...****
>
> ** **
>
> *6 instances of Missing Patch File*****
>
> ** **
>
> Errors look similar to:****
>
> ** **
>
> [ 12s] + exec rpmbuild --define '_srcdefattr (-,root,root)'
> --nosignature --target=i686-tizen-linux --define '_build_create_debug 1'
> -ba /home/abuild/rpmbuild/SOURCES/cross-armv5el-gcc47-icecream-backend.spec
> ****
>
> [ 12s] error: Bad source:
> /home/abuild/rpmbuild/SOURCES/0001-dir-version.patch: No such file or
> directory****
>
> [ 12s] Building target platforms: i686-tizen-linux****
>
> [ 12s] Building for target i686-tizen-linux****
>
> ** **
>
> I'm not sure that understand why there would ever be a patch file
> here--Isn't the goal to have everything in the original sources?****
>
> ** **
>
> *7 instances of some other file missing*****
>
> ** **
>
> Errors like:****
>
> ** **
>
> [ 4s] reqesting
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages/repodata/repomd.xmlfailed:
> 404 Not Found
> ****
>
> [ 4s] Couldn't open
> /home/phanchet/GBS-TIZEN-3.0M2/local/cache/0cca4ce1752580229c4256e2194fb1e7/repodata/repomd.xml:
> ****
>
> [ 4s] No such file or directory at /usr/lib/build/createrepomddeps line
> 436****
>
> ** **
>
> a****
>
> nd:****
>
> ** **
>
> ** **
>
> [ 45s] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I..
> -D_LARGEFILE_SOURCE=1 -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -D_REENTRANT
> -DXTABLES_LIBDIR=\"/usr/lib/xtables\" -DXTABLES_INTERNAL -I../include
> -I../include -Wall -Waggregate-return -Wmissing-declarations
> -Wmissing-prototypes -Wredundant-decls -Wshadow -Wstrict-prototypes
> -Winline -pipe -O2 -g -m32 -march=i686 -mtune=i686 -fmessage-length=0
> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
> -fasynchronous-unwind-tables -MT libipq.lo -MD -MP -MF .deps/libipq.Tpo -c
> libipq.c -fPIC -DPIC -o .libs/libipq.o****
>
> [ 45s] In file included from libipq.c:34:0:****
>
> [ 45s] ../include/libipq/libipq.h:33:43: fatal error:
> linux/netfilter_ipv4/ip_queue.h: No such file or directory****
>
> [ 45s] compilation terminated.****
>
> [ 45s] make[2]: *** [libipq.lo] Error 1****
>
> [ 45s] make[2]: Leaving directory
> `/home/abuild/rpmbuild/BUILD/iptables-1.4.14/libipq'****
>
> [ 45s] make[1]: *** [all-recursive] Error 1****
>
> [ 45s] make[1]: Leaving directory
> `/home/abuild/rpmbuild/BUILD/iptables-1.4.14'****
>
> [ 45s] make: *** [all] Error 2****
>
> [ 45s] error: Bad exit status from /var/tmp/rpm-tmp.k2HLdr (%build)****
>
> ** **
>
> and:****
>
> ** **
>
> [ 68s] + exec rpmbuild --define '_srcdefattr (-,root,root)'
> --nosignature --target=i686-tizen-linux --define '_build_create_debug 1'
> -ba /home/abuild/rpmbuild/SOURCES/python-rpm.spec****
>
> [ 68s] error: File /home/abuild/rpmbuild/SOURCES/rpm-4.11.0.1.tar.bz2:
> No such file or directory****
>
> [ 68s] Building target platforms: i686-tizen-linux****
>
> [ 68s] Building for target i686-tizen-linux****
>
> ** **
>
> *2 instances of Nothing Provides*****
>
> ** **
>
> [ 1s] nothing provides libcurl.so.4(CURL_OPENSSL_4) needed by cmake
> ****
>
> ** **
>
> and****
>
> ** **
>
> [ 8s] nothing provides xorg-launch-helper****
>
> ** **
>
> *1 unique error*****
>
> ** **
>
> Finally:****
>
> ** **
>
> [ 21s] now finalizing build dir...****
>
> [ 21s] chroot: failed to run command `su': No such file or directory****
>
> [ 21s] Error: TOPDIR empty****
>
> ** **
>
> *Other Observations:*****
>
> ** **
>
> I also thought I noticed several places where there were strong warnings
> in RPM build code as well as in the sources for the package being built-- I
> don't have specific references at the moment, but I'll note that there are
> so many "normal" errors being reported that it's hard to spot the true
> trouble spots that need attention.****
>
> ** **
>
> ** **
>
> *Analysis and Conclusions:*****
>
> ** **
>
> We've taken pains to try to ensure that we started with a single cohesive
> set of sources, specifically those for the Aug M2 release of Tizen. At the
> bottom, everything is built with make files under the supervision of
> rpmbuild, with gbs (or obs) on top of that. Given the same sources, I
> really expect rpmbuild to produce the same result regardless of how it's
> started.****
>
> ** **
>
> ***IF*** we are starting with the same sources (remember, that was our
> intent at the top of this missive), then it's quite difficult to understand
> why we aren't able to replicate the successful build (on obs) of these
> packages.****
>
> ** **
>
> Looking at the errors themselves, all of the files referring to libstdc++
> that built refer to the 4.7 version of the library while the files with
> errors seem to be trying to refer to the 4.8 version of the library. ****
>
> ** **
>
> Patch files clearly have been removed without updating the corresponding
> spec files. File missing and nothing provides are also variations of the
> build meta-system being out of sync with itself.****
>
> ** **
>
> The point is that the errors we are seeing will always be fatal to the
> build, regardless of how it is initiated.****
>
> ** **
>
> So, I'm wondering what have I done wrong? The full failure logs are
> attached.****
>
> ** **
>
> I'm wondering if it's possible to review the success and failure logs from
> the obs build so I can compare with what I have here?****
>
> ** **
>
> TIA for your thoughts!****
>
> ** **
>
>
> 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****
>
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
