Date
1 - 10 of 10
Build failures on yocto
|
Hector Oron <hector.oron@...>
#! /bin/sh
# Hello, case $Debian_build_system in lenny_amd64) cat <<EOF [...] | /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/git/target-arm/dummygl.c:5:22: warning: X11/Xlib.h: No such file or directory | /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/git/target-arm/dummygl.c:6:23: warning: X11/Xutil.h: No such file or directory | /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/git/target-arm/dummygl.c:8: error: expected ')' before '*' token | /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/git/target-arm/dummygl.c:13: warning: no previous prototype for 'opengl_process_enable' | /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/git/target-arm/dummygl.c:19: warning: no previous prototype for 'mem_opengl' | make[1]: *** [dummygl.o] Error 1 | make[1]: Leaving directory `/srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/git/arm-linux-user' | make: *** [subdir-arm-linux-user] Error 2 | FATAL: oe_runmake failed NOTE: Task failed: /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5/temp/log.do_compile.28106 NOTE: package qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57-r5: task do_compile: failed ERROR: TaskFailed event exception, aborting NOTE: package qemu-native-0.10.2+git9eab386edbf8cf002a731f8204a156f243a47a57: failed ERROR: Build of /srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/meta/packages/qemu/qemu-native_git.bb do_compile failed ERROR: Task 597 (/srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/meta/packages/qemu/qemu-native_git.bb, do_compile) failed NOTE: Tasks Summary: Attempted 229 tasks of which 0 didn't need to be rerun and 1 failed. ERROR: '/srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/meta/packages/qemu/qemu-native_git.bb' failed NOTE: build 201011011610: completed make: *** [/srv/build/builds/menuconfig2-test/build/rootfs/yocto/purple-3.2/foo] Error 1 EOF ;; lenny_i386) cat <<EOF [...] | NOTE: Running /srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/gmp-native-4.2.4-r0/gmp-4.2.4/configure --build=x86_64-linux --host=x86_64-linux --target=x86_64-linux --prefix=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr --exec_prefix=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr --bindir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/bin --sbindir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/sbin --libexecdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/libexec --datadir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share --sysconfdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/etc --sharedstatedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/com --localstatedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/var --libdir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/lib --includedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/include --oldincludedir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/include --infodir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share/info --mandir=/srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/staging/x86_64-linux/usr/share/man ... | checking build system type... x86_64-pc-linux-gnu | checking host system type... x86_64-pc-linux-gnu | checking for a BSD-compatible install... /usr/bin/install -c [...] | checking size of unsigned short... 2 | checking for unsigned... yes | checking size of unsigned... 4 | checking for unsigned long... yes | checking size of unsigned long... 4 | checking for mp_limb_t... yes | checking size of mp_limb_t... 4 | configure: error: Oops, mp_limb_t is 32 bits, but the assembler code | in this configuration expects 64 bits. | You appear to have set $CFLAGS, perhaps you also need to tell GMP the | intended ABI, see "ABI and ISA" in the manual. | FATAL: oe_runconf failed NOTE: Task failed: /srv/build/builds/build/rootfs/yocto/purple-3.2/build/tmp/work/x86_64-linux/gmp-native-4.2.4-r0/temp/log.do_configure.28892 NOTE: package gmp-native-4.2.4-r0: task do_configure: failed ERROR: TaskFailed event exception, aborting NOTE: package gmp-native-4.2.4: failed ERROR: Build of /srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb do_configure failed ERROR: Task 556 (/srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb, do_configure) failed NOTE: Tasks Summary: Attempted 135 tasks of which 135 didn't need to be rerun and 1 failed. ERROR: '/srv/build/builds/build/rootfs/yocto/purple-3.2/meta/packages/gmp/gmp-native_4.2.4.bb' failed NOTE: build 201011011717: completed make: *** [/srv/build/builds/menuconfig2-i386/../build/rootfs/yocto/purple-3.2/foo] Error 1 EOF ;; unstable_amd64) cat <<EOF Still building...... EOF ;; unstable_i386) cat <<EOF [...] | checking size of unsigned long... 4 | checking size of mp_limb_t... 4 | configure: error: Oops, mp_limb_t is 32 bits, but the assembler code | in this configuration expects 64 bits. | You appear to have set $CFLAGS, perhaps you also need to tell GMP the | intended ABI, see "ABI and ISA" in the manual. | FATAL: oe_runconf failed | ERROR: Task failed: ('function do_configure failed', '/srv/build/builds/build/rootfs/yocto/laverne-4.0/build/tmp/work/x86_64-linux/gmp-native-5.0.1-r0/temp/log.do_configure.13641') NOTE: package gmp-native-5.0.1-r0: task do_configure: Failed ERROR: Task 971 (virtual:native:/srv/build/builds/build/rootfs/yocto/laverne-4.0/meta/recipes-support/gmp/gmp_5.0.1.bb, do_configure) failed with 1 Waiting for 1 active tasks to finish: 1: gettext-native-0.17-r5 do_compile (pid 13646) NOTE: package gettext-native-0.17-r5: task do_compile: Succeeded ERROR: 'virtual:native:/srv/build/builds/build/rootfs/yocto/laverne-4.0/meta/recipes-support/gmp/gmp_5.0.1.bb' failed make: *** [/srv/build/builds/menuconfig2-i386/../build/rootfs/yocto/laverne-4.0/foo] Error 1 EOF ;; others|*) cat <<EOF - I need to setup "vm.mmap_min_addr = 0" under /etc/sysctl.conf - sh linked to dash makes build system fail (./build/rootfs/yocto/laverne-4.0/poky-init-build-env): (sid_i386)zumbi@enorme:/srv/build/builds/build/rootfs/yocto/laverne-4.0$ checkbashisms poky-init-build-env possible bashism in poky-init-build-env line 24 ($BASH_SOMETHING): elif test x"$BASH_SOURCE" = x; then possible bashism in poky-init-build-env line 27 ($BASH_SOMETHING): . `dirname $BASH_SOURCE`/scripts/poky-env-internal - On lenny python 2.5 required, so Purple 3.2 was built (Laverne was not tried) - On unstable Laverne 4.0 was attempted EOF ;; esac echo "Have a nice day!" -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash # ^^^^^----- I had to change it so I could build on unstable ;-) -- Héctor Orón "Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us." -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html |
|
|
|
Richard Purdie <rpurdie@...>
Hi,
I don't have answers to all of the failures but let me try and respond to the ones I have some ideas about: On Mon, 2010-11-01 at 18:23 +0000, Hector Oron wrote: lenny_i386)At a guess this is a 64 bit kernel and a 32 bit userspace? What does "uname -a" show? I suspect if you add BUILD_ARCH = "i686" to your local.conf, the build might work better? If you can confirm that we can probably detect this problem and avoid this failure. ;;Same as the above failure (64 bit kernel and 32 bit userspace)? ;;Right, but it detected that? - sh linked to dash makes build system failOuch. We don't support building with /bin/sh as dash (way too many broken scripts our there still) and the system would tell you as such if it detected that. Looks like bashisms have made it into the setup script though which we need to fix. Cheers, Richard |
|
|
|
Hector Oron <hector.oron@...>
Hi,
2010/11/1 Hector Oron <hector.oron@...>: #! /bin/sh case $Debian_build_system inNOTE: package libtool-cross-2.2.10-r1: task do_package_write: Succeeded NOTE: Running task 1448 of 1529 (ID: 433, /srv/build/builds/menuconfig2-test/build/rootfs/yocto/laverne-4.0/meta/recipes-kernel/linux/linux-dummy.bb, do_package_write_ipk) NOTE: package linux-dummy-1.0-r1: task do_package_write_ipk: Started ERROR: Task failed: opkg-build execution failed NOTE: package linux-dummy-1.0-r1: task do_package_write_ipk: Failed ERROR: Task 433 (/srv/build/builds/menuconfig2-test/build/rootfs/yocto/laverne-4.0/meta/recipes-kernel/linux/linux-dummy.bb, do_package_write_ipk) failed with 1 Waiting for 1 active tasks to finish: 1: perl-5.8.8-r20 do_package_write_ipk (pid 6797) NOTE: Not creating empty archive for perl-module-cgi-eg-make-links-5.8.8-r20 NOTE: package perl-5.8.8-r20: task do_package_write_ipk: Succeeded ERROR: '/srv/build/builds/menuconfig2-test/build/rootfs/yocto/laverne-4.0/meta/recipes-kernel/linux/linux-dummy.bb' failed make: *** [/srv/build/builds/menuconfig2-test/build/rootfs/yocto/laverne-4.0/foo] Error 1 EOFBest regards, |
|
|
|
Richard Purdie <rpurdie@...>
On Tue, 2010-11-02 at 09:17 +0000, Hector Oron wrote:
Hi,Which MACHINE is that set for? Its unusual for the system to be using linux-dummy. Cheers, Richard |
|
|
|
Hector Oron <hector.oron@...>
Hello,
2010/11/1 Richard Purdie <rpurdie@...>: I don't have answers to all of the failures but let me try and respond On Mon, 2010-11-01 at 18:23 +0000, Hector Oron wrote:Yes, it is 64 bit kernel host running a 32 bit userland.lenny_i386)At a guess this is a 64 bit kernel and a 32 bit userspace? What does Linux enorme 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux I suspect if you addBuild attempted with BUILD_ARCH="i686" BB_NUMBER_THREADS="2" PARALLEL_MAKE="-j 2" MACHINE=$(BOARD) bitbake $(YOCTO_IMAGE) got same result as above. Same as the above failure (64 bit kernel and 32 bit userspace)?Sure. If it was not set, scripts warn about it, once you set it up, it goes through.others|*)Right, but it detected that? Best regards, -- Héctor Orón "Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us." -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html |
|
|
|
Hector Oron <hector.oron@...>
Hello,
2010/11/2 Richard Purdie <rpurdie@...>: Which MACHINE is that set for? Its unusual for the system to be usingIt is a balloon3 [1]. I think you have not official support for it. I also got an Intel Embedded Devkit 1-N450 (Black Sand) which I could attempt to build for it. [1] http://balloonboard.org/ Best regards, -- Héctor Orón "Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us." -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html |
|
|
|
Richard Purdie <rpurdie@...>
On Tue, 2010-11-02 at 10:03 +0000, Hector Oron wrote:
Only certainly variables can be passed through the environment. Can youAt a guess this is a 64 bit kernel and a 32 bit userspace? What doesYes, it is 64 bit kernel host running a 32 bit userland. put the line in local.conf please and retry as otherwise it won't have any effect. Ok, good.Same as the above failure (64 bit kernel and 32 bit userspace)?Sure.If it was not set, scripts warn about it, once you set it up, it goes through.others|*)Right, but it detected that? Cheers, Richard |
|
|
|
Richard Purdie <rpurdie@...>
On Tue, 2010-11-02 at 10:08 +0000, Hector Oron wrote:
Hello,So to be clear, you set MACHINE="balloon3"? You're therefore building with some layer or additional metadata? I'd suggest trying a supported machine like "atom-pc" first before trying to add your own. Cheers, Richard |
|
|
|
Hector Oron <hector.oron@...>
Hello,
2010/11/2 Richard Purdie <rpurdie@...>: So to be clear, you set MACHINE="balloon3"? You're therefore buildingYes and yes. I'll attempt "atom-pc" later on, but that is not much of interest for me. Thanks. Best regards, -- Héctor Orón "Our Sun unleashes tremendous flares expelling hot gas into the Solar System, which one day will disconnect us." -- Day DVB-T stop working nicely Video flare: http://antwrp.gsfc.nasa.gov/apod/ap100510.html |
|
|
|
Richard Purdie <rpurdie@...>
On Tue, 2010-11-02 at 11:39 +0000, Hector Oron wrote:
2010/11/2 Richard Purdie <rpurdie@...>:I'd just appreciate people being a little clearer about what they'reSo to be clear, you set MACHINE="balloon3"? You're therefore buildingYes and yes. I'll attempt "atom-pc" later on, but that is not much of attempting to do. Obviously I don't know how you've setup this balloon3 target but knowing this isn't an out the box configuration might help me target my replies to you. There would appear to be a problem with the kernel provision for your board. As a hint, either have a kernel recipe and point to it with PREFERRED_PROVIDER_virtual/kernel setting in the machine configuration or ensure the machine in question is listed in COMPATIBLE_MACHINE of the kernel recipe you want to use. Cheers, Richard |
|
|