Bug 950 - meta-toolchain-sdk build failure
Summary: meta-toolchain-sdk build failure
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.0-alpha
Hardware: Beagleboard arm
: Medium normal
Target Milestone: 1.1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-04-04 13:16 UTC by Robert Berger
Modified: 2011-08-05 07:40 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Berger 2011-04-04 13:16:46 UTC
I build a poky-image-lsb-sdk (succeeds) followed by a meta-toolchain-sdk(fails)

commit bcc817ee058bbab91d6e88a3e1e867a4ff09aeca
Thu Mar 31 13:31:27 2011

OE Build Configuration:
BB_VERSION        = "1.11.0"
METADATA_BRANCH   = "latest-2011-04-02_LOCAL"
METADATA_REVISION = "bcc817ee058bbab91d6e88a3e1e867a4ff09aeca"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.0+snapshot-20110404"
TARGET_FPU        = "soft"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 665 of 3651 (ID: 3262, /work/rber/poky/meta/recipes-devtools/gcc/gcc-crosssdk-initial_4.5.1.bb, do_compile)
NOTE: package gcc-crosssdk-initial-4.5.1-r4: task do_compile: Started
ERROR: Function 'do_compile' failed (see /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/temp/log.do_compile.10771 for further information)
ERROR: Logfile of failure stored in: /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/temp/log.do_compile.10771
Log data follows:
| NOTE: make ARCH_FLAGS_FOR_TARGET= -isystem/work/rber/poky-latest-build-bb/tmp/sysroots/i686-nativesdk-pokysdk-linux/opt/poky/1.0+snapshot/sysroots/i686-pokysdk-linux${includedir_nativesdk}
| make[1]: Entering directory `/work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/build.i686-linux.i686-pokysdk-linux'
| make[2]: Entering directory `/work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/build.i686-linux.i686-pokysdk-linux/libiberty'
| if [ x"" != x ]; then \
| 	  gcc -c -DHAVE_CONFIG_H -isystem/work/rber/poky-latest-build-bb/tmp/sysroots/i686-linux/usr/include -O2 -pipe  -I. -I/work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/../include  -W -Wwrite-strings  /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c -o pic/fibheap.o; \
| 	else true; fi
| gcc -c -DHAVE_CONFIG_H -isystem/work/rber/poky-latest-build-bb/tmp/sysroots/i686-linux/usr/include -O2 -pipe  -I. -I/work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/../include  -W -Wwrite-strings /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c -o fibheap.o
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c: In function 'fibheap_replace_key_data':
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c:220: error: 'LONG_MIN' undeclared (first use in this function)
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c:220: error: (Each undeclared identifier is reported only once
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c:220: error: for each function it appears in.)
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c: In function 'fibheap_delete_node':
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c:261: error: 'LONG_MIN' undeclared (first use in this function)
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c: In function 'fibheap_consolidate':
| /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/libiberty/fibheap.c:368: warning: incompatible implicit declaration of built-in function 'memset'
| make[2]: *** [fibheap.o] Error 1
| make[2]: Leaving directory `/work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/gcc-4.5.1/build.i686-linux.i686-pokysdk-linux/libiberty'
| make[1]: *** [all-libiberty] Error 2
| ERROR: Function 'do_compile' failed (see /work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk-linux/gcc-crosssdk-initial-4.5.1-r4/temp/log.do_compile.10771 for further information)
| make[1]: Leaving directory `/work/rber/poky-latest-build-bb/tmp/work/i686-pokysdk
NOTE: package gcc-crosssdk-initial-4.5.1-r4: task do_compile: Failed
ERROR: Task 3262 (/work/rber/poky/meta/recipes-devtools/gcc/gcc-crosssdk-initial_4.5.1.bb, do_compile) failed with exit code '1'
NOTE: Running noexec task 2251 of 3651 (ID: 1211, virtual:nativesdk:/work/rber/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_package_write)
NOTE: Running task 2252 of 3651 (ID: 1178, /work/rber/poky/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb, do_package_write_rpm)
NOTE: package binutils-crosssdk-2.21-r0: task do_package_write_rpm: Started
NOTE: package binutils-crosssdk-2.21-r0: task do_package_write_rpm: Succeeded
NOTE: Running noexec task 2253 of 3651 (ID: 1175, /work/rber/poky/meta/recipes-devtools/binutils/binutils-crosssdk_2.21.bb, do_package_write)
NOTE: Running task 2433 of 3651 (ID: 927, virtual:nativesdk:/work/rber/poky/meta/recipes-devtools/qemu/qemu_0.14.0.bb, do_patch)
NOTE: package qemu-nativesdk-0.14.0-r0: task do_patch: Started
ERROR: Cannot proceed with manual patch resolution - 'gnome-terminal --disable-factory -t "$TERMWINDOWTITLE" -x $SHELLCMDS' not found. Check TERMCMDRUN variable.
ERROR: Function 'patch_do_patch' failed
ERROR: Logfile of failure stored in: /work/rber/poky-latest-build-bb/tmp/work/i686-nativesdk-pokysdk-linux/qemu-nativesdk-0.14.0-r0/temp/log.do_patch.10830
Log data follows:
| NOTE: Applying patch 'qemu-git-qemugl-host.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/qemu-git-qemugl-host.patch)
| NOTE: Applying patch 'no-strip.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/no-strip.patch)
| NOTE: Applying patch 'fix-nogl.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/fix-nogl.patch)
| NOTE: Applying patch 'qemugl-allow-glxcontext-release.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/qemugl-allow-glxcontext-release.patch)
| NOTE: Applying patch 'linker-flags.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/linker-flags.patch)
| NOTE: Applying patch 'init-info.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/init-info.patch)
| NOTE: Applying patch 'qemu-vmware-vga-depth.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/qemu-vmware-vga-depth.patch)
| NOTE: Applying patch 'enable-i386-linux-user.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/enable-i386-linux-user.patch)
| NOTE: Applying patch 'fix-configure-checks.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/fix-configure-checks.patch)
| NOTE: Applying patch 'fallback-to-safe-mmap_min_addr.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/fallback-to-safe-mmap_min_addr.patch)
| NOTE: Applying patch 'spice-qxl-locking-fix-for-qemu-kvm.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/spice-qxl-locking-fix-for-qemu-kvm.patch)
| NOTE: Applying patch 'Detect-and-use-GCC-atomic-builtins-for-locking.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/Detect-and-use-GCC-atomic-builtins-for-locking.patch)
| NOTE: Applying patch 'larger_default_ram_size.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/larger_default_ram_size.patch)
| NOTE: Applying patch 'glflags.patch' (../poky/meta/recipes-devtools/qemu/qemu-0.14.0/glflags.patch)
| Failed to summon the GConf demon; exiting.  Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Command line `dbus-launch --autolaunch=acf555838e8a1e87f5fdcc7400000003 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch requested, but X11 support not compiled in.\nCannot continue.\n)
| ERROR: Cannot proceed with manual patch resolution - 'gnome-terminal --disable-factory -t "$TERMWINDOWTITLE" -x $SHELLCMDS' not found. Check TERMCMDRUN variable.
| ERROR: Function 'patch_do_patch' failed
NOTE: package qemu-nativesdk-0.14.0-r0: task do_patch: Failed
ERROR: Task 927 (virtual:nativesdk:/work/rber/poky/meta/recipes-devtools/qemu/qemu_0.14.0.bb, do_patch) failed with exit code '1'
NOTE: Running task 2714 of 3651 (ID: 1042, /work/rber/poky/meta/recipes-core/meta/meta-environment.bb, do_generate_content)
Comment 1 Robert Berger 2011-04-05 02:57:58 UTC
also with commit f897723207b00b4c9dcdb43107891b7b82ce22f3
Tue Mar 29 12:55:18 2011 -0700

meta-toolchain-sdk does __NOT__ build for beagleboard and routerstation pro
Comment 2 Robert Berger 2011-04-05 20:55:40 UTC
http://permalink.gmane.org/gmane.linux.embedded.poky/5075 improves things

It should be on the master branch in the meantime:
http://permalink.gmane.org/gmane.linux.embedded.poky/5122 

I'll try again with a new git pull from master.
Comment 3 Richard Purdie 2011-05-06 14:20:25 UTC
How is this looking with master now? Could you report the current status please as it seems some issues should have been fixed at least.
Comment 4 Richard Purdie 2011-08-05 07:40:10 UTC
I think all the issues mentioned here have been resolved. If there are any problems you can reproduce against master, please reopen or file a new bug.