Doing a fresh build, starting from a bare metal machine. So I used this article<https://developer.tizen.org/help/topic/org.tizen.platform.development/html/platform_dev_env/gerrit_ssh.htm>to set up my ssh, and this one to use repo to get the source<https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build>tree (section 2 of the document), gbs previously set up. As best I understand, I'm grabbing the tizen branch so I think I'm looking at Tizen 3.0/IVI. Ran
cd ~/Tizen_3-0 gbs build -A i586 And OH BOY: It starts to build! Joy Joy! [?] Then gbs terminates with an error: [?] === the following packages failed to build due to rpmbuild issue (18) === e2fsprogs-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/e2fsprogs-1.42.6-0/log hunspell-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/hunspell-1.3.2-0/log libtirpc-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/libtirpc-0.2.2-0/log man-db-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/man-db-2.6.3-1/log perl-Error-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/perl-Error-0.17017-7/log libSM-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/libSM-1.2.1-0/log eject-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/eject-2.1.5-25/log perl-URI-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/perl-URI-1.60-1/log cloog-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/cloog-0.15.10-0/log perl-Switch-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/perl-Switch-2.16-4/log sys-string-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/sys-string-1.1-2/log docbook_4-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/docbook_4-4.5-0/log build-initvm-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/build-initvm-20120927-0/log mmfw-sysconf-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/mmfw-sysconf-0.1.66-0/log perl-X11-Protocol-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/perl-X11-Protocol-0.56-1/log libusb-compat-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/libusb-compat-0.1.4-2/log libgpg-error-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/libgpg-error-1.10-0/log powertop-tizen3.0-i586: /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail/powertop-2.3-1/log error: <gbs>rpmbuild fails administrator@tizen-SDK-2:~/Tizen_3-0$ Sample log from first file above: [ 0s] Memory limit set to 4528244KB [ 0s] Using BUILD_ROOT=/home/administrator/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.0 [ 0s] Using BUILD_ARCH=i686:i586:i486:i386:noarch [ 0s] [ 0s] [ 0s] tizen-SDK-2 started "build e2fsprogs.spec" at Wed Aug 21 17:57:35 UTC 2013. [ 0s] [ 0s] [ 0s] processing specfile /home/administrator/GBS-ROOT/local/sources/tizen3.0/e2fsprogs-1.42.6-0/e2fsprogs.spec ... [ 0s] init_buildsystem --configdir /var/tmp/administrator-gbs --cachedir /home/administrator/GBS-ROOT/local/cache --repository /home/administrator/GBS-ROOT/local/repos/tizen3.0/i586/RPMS --repository /home/administrator/Tizen_3-0/pre-built/toolchain-x86/ /home/administrator/GBS-ROOT/local/sources/tizen3.0/e2fsprogs-1.42.6-0/e2fsprogs.spec ... [ 0s] expanding package dependencies... [ 0s] expansion error [ 0s] nothing provides libsmack.so.1(LIBSMACK) needed by rpm-security-plugin libsmack.so.1 seems to be missing. Did a find for the .so and it's missing. Looked for error logs on libsmack and didn't really find anything. I did find some jira references to it missing in the build but they seemed pretty old... I did see some comments along the line 'It's mssing but it's turned off so it shouldn't harm anyone.' I see closed bug TIVI-912 that indicates that someone has tested the feature, but it doesn't seem to generate any artifacts on my build system. So, some questions (I'm sure there are more): 1. How do I fix the immediate error? 2. Is this a bug in how tizen 3.0 is being built? TIA for any help you can offer! 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
<<362.gif>>
<<360.gif>>
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
