* sstate breakage with multimachine
@ 2011-05-16 11:20 Koen Kooi
2011-05-16 23:13 ` Richard Purdie
2011-05-17 7:14 ` Martin Jansa
0 siblings, 2 replies; 9+ messages in thread
From: Koen Kooi @ 2011-05-16 11:20 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Hi,
This bug gets reintroduced every other week, so let's try to fix it properly this time. The situation:
2 machines (beagleboard, pandaboard) using the same base architecture (armv7a).
step 0: rm build pseudone -rf
step 1: MACHINE=beagleboard bitbake console-image
step 2: MACHINE=omap4430-panda bitbake console-image
Step 0 and 1 work great, but I can't get step 2 to work. Attached is the complete output of step 2. As you can see without any updates to the repositories it wants to rebuild (e)glibc.
Why does it wants to rebuild all that? Why does it fail?
regards,
Koen
[-- Attachment #2: panda-build.log.txt --]
[-- Type: text/plain, Size: 49744 bytes --]
Configured layers:
layer repository name: bitbake
layer uri: git://git.openembedded.net/bitbake
layer branch/revision: master/HEAD
Updating layer at layers/bitbake
Current branch master is up to date.
Layers present in repository:
layer repository name: openembedded-core
layer uri: git://git.openembedded.org/openembedded-core
layer branch/revision: master/HEAD
Updating layer at layers/openembedded-core
Current branch master is up to date.
Layers present in repository:
openembedded-core/meta
openembedded-core/meta-rt
layer repository name: meta-angstrom
layer uri: git://git.angstrom-distribution.org/meta-angstrom
layer branch/revision: master/HEAD
Updating layer at layers/meta-angstrom
Current branch master is up to date.
Layers present in repository:
meta-angstrom
layer repository name: meta-openembedded
layer uri: git://git.openembedded.net/meta-openembedded
layer branch/revision: master/HEAD
Updating layer at layers/meta-openembedded
Current branch master is up to date.
Layers present in repository:
meta-openembedded/meta-efl
meta-openembedded/meta-oe
meta-openembedded/meta-gnome
meta-openembedded/meta-gpe
layer repository name: meta-texasinstruments
layer uri: git://git.angstrom-distribution.org/meta-texasinstruments
layer branch/revision: master/HEAD
Updating layer at layers/meta-texasinstruments
Current branch master is up to date.
Layers present in repository:
meta-texasinstruments
Using /home/koen/.oe/environment-oecore to setup needed variables. It is recommended to do '. /home/koen/.oe/environment-oecore' and run 'bitbake something' without using ./oebb.sh as wrapper
Executing: MACHINE=omap4430-panda bitbake console-image
Parsing recipes...NOTE: Angstrom DOES NOT support libiconv because the eglibc provided iconv library is used
NOTE: Angstrom DOES NOT support gconf-dbus because gconf-dbus has been merged back into main GConf
NOTE: Angstrom DOES NOT support gconf-dbus-native because gconf-dbus has been merged back into main GConf
NOTE: Angstrom DOES NOT support libiconv because the eglibc provided iconv library is used
done.
Parsing of 1148 .bb files complete (0 cached, 1148 parsed). 1483 targets, 41 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for runtime psplash-support (psplash, psplash-angstrom, psplash-omap3pandora, psplash-ti)
NOTE: consider defining a PREFERRED_PROVIDER entry to match psplash-support
NOTE: Preparing runqueue
ERROR: Multiple .bb files are due to be built which each provide virtual/psplash (/OE/tentacle/sources/meta-angstrom/recipes-core/psplash/psplash-angstrom_svn.bb /OE/tentacle/sources/meta-angstrom/recipes-core/psplash/psplash_svn.bb).
This usually means one provides something the other doesn't and should.
ERROR: Multiple .bb files are due to be built which each provide ssh (/OE/tentacle/sources/openembedded-core/meta/recipes-core/dropbear/dropbear_0.52.bb /OE/tentacle/sources/openembedded-core/meta/recipes-connectivity/openssh/openssh_5.6p1.bb).
This usually means one provides something the other doesn't and should.
ERROR: Multiple .bb files are due to be built which each provide sshd (/OE/tentacle/sources/openembedded-core/meta/recipes-core/dropbear/dropbear_0.52.bb /OE/tentacle/sources/openembedded-core/meta/recipes-connectivity/openssh/openssh_5.6p1.bb).
This usually means one provides something the other doesn't and should.
NOTE: Executing SetScene Tasks
OE Build Configuration:
BB_VERSION = "1.13.0"
METADATA_BRANCH = "master"
METADATA_REVISION = "ace08f0395e64800cab55eeb30469bb73f94fcca"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "omap4430-panda"
DISTRO = "angstrom"
DISTRO_VERSION = "v2011.05-core"
TARGET_FPU = "hard"
NOTE: package initscripts-1.0-r125: task do_populate_sysroot_setscene: Started
NOTE: package udev-165-r2: task do_populate_sysroot_setscene: Started
NOTE: package tinylogin-1.4-r6: task do_populate_sysroot_setscene: Started
NOTE: package psplash-zap-1.0-r7: task do_populate_sysroot_setscene: Started
NOTE: package initscripts-1.0-r125: task do_populate_sysroot_setscene: Succeeded
NOTE: package tinylogin-1.4-r6: task do_populate_sysroot_setscene: Succeeded
NOTE: package psplash-zap-1.0-r7: task do_populate_sysroot_setscene: Succeeded
NOTE: package udev-165-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package opkg-1_0.1.8+svnr596-r2: task do_populate_sysroot_setscene: Started
NOTE: package dropbear-0.52-r1: task do_populate_sysroot_setscene: Started
NOTE: package wireless-tools-1_29-r1: task do_populate_sysroot_setscene: Started
NOTE: package dropbear-0.52-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package wpa-supplicant-0.7.3-r4: task do_populate_sysroot_setscene: Started
NOTE: package opkg-1_0.1.8+svnr596-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package wireless-tools-1_29-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package util-linux-2.17.2-r7: task do_populate_sysroot_setscene: Started
NOTE: package portmap-6.0-r7: task do_populate_sysroot_setscene: Started
NOTE: package wpa-supplicant-0.7.3-r4: task do_populate_sysroot_setscene: Succeeded
NOTE: package portmap-6.0-r7: task do_populate_sysroot_setscene: Succeeded
NOTE: package util-linux-2.17.2-r7: task do_populate_sysroot_setscene: Succeeded
NOTE: package angstrom-libc-fixup-hack-1.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package angstrom-libc-fixup-hack-1.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package bluez4-4.91-r9: task do_populate_sysroot_setscene: Started
NOTE: package apmd-3.2.2-14-r1: task do_populate_sysroot_setscene: Started
NOTE: package ppp-2.4.5-r1: task do_populate_sysroot_setscene: Started
NOTE: package ppp-dialin-0.1-r6: task do_populate_sysroot_setscene: Started
NOTE: package ppp-2.4.5-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package apmd-3.2.2-14-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package ppp-dialin-0.1-r6: task do_populate_sysroot_setscene: Succeeded
NOTE: package bluez4-4.91-r9: task do_populate_sysroot_setscene: Succeeded
NOTE: package usbutils-0.86-r1: task do_populate_sysroot_setscene: Started
NOTE: package e2fsprogs-1.41.14-r0: task do_populate_sysroot_setscene: Started
NOTE: package alsa-utils-1.0.24.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package usbutils-0.86-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package sysfsutils-2.1.0-r1: task do_populate_sysroot_setscene: Started
NOTE: package alsa-utils-1.0.24.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package e2fsprogs-1.41.14-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package sysfsutils-2.1.0-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package module-init-tools-3.12-r1: task do_populate_sysroot_setscene: Started
NOTE: package module-init-tools-3.12-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package avahi-0.6.30-r0: task do_populate_sysroot_setscene: Started
NOTE: package openssh-5.6p1-r1: task do_populate_sysroot_setscene: Started
NOTE: package openssh-5.6p1-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package strace-4.5.20-r1: task do_populate_sysroot_setscene: Started
NOTE: package procps-3.2.8-r1: task do_populate_sysroot_setscene: Started
NOTE: package strace-4.5.20-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package procps-3.2.8-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package update-rc.d-0.7-r3: task do_populate_sysroot_setscene: Started
NOTE: package update-rc.d-0.7-r3: task do_populate_sysroot_setscene: Succeeded
NOTE: package psplash-angstrom-0.0+svnr422-r34: task do_populate_sysroot_setscene: Started
NOTE: package psplash-angstrom-0.0+svnr422-r34: task do_populate_sysroot_setscene: Succeeded
NOTE: package gcc-cross-4.5-r36.2: task do_populate_sysroot_setscene: Started
NOTE: package avahi-0.6.30-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gcc-runtime-4.5-r36.1: task do_populate_sysroot_setscene: Started
NOTE: package eglibc-2.12-r13: task do_populate_sysroot_setscene: Started
NOTE: package mtd-utils-1.4.1-r1: task do_populate_sysroot_setscene: Started
NOTE: package mtd-utils-1.4.1-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package makedevs-1.0.0-r7: task do_populate_sysroot_setscene: Started
NOTE: package makedevs-1.0.0-r7: task do_populate_sysroot_setscene: Succeeded
NOTE: package libtool-cross-2.4-r2: task do_populate_sysroot_setscene: Started
NOTE: package libtool-cross-2.4-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package acl-2.2.51-r0: task do_populate_sysroot_setscene: Started
NOTE: package acl-2.2.51-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gcc-runtime-4.5-r36.1: task do_populate_sysroot_setscene: Succeeded
NOTE: package gcc-cross-4.5-r36.2: task do_populate_sysroot_setscene: Succeeded
NOTE: package glib-2.0-1_2.28.6-r1: task do_populate_sysroot_setscene: Started
NOTE: package gpgme-1.3.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package curl-7.21.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package curl-7.21.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package openssl-1.0.0c-r13.2: task do_populate_sysroot_setscene: Started
NOTE: package gpgme-1.3.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package zlib-1.2.5-r0: task do_populate_sysroot_setscene: Started
NOTE: package eglibc-2.12-r13: task do_populate_sysroot_setscene: Succeeded
NOTE: package glib-2.0-1_2.28.6-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package dbus-1.2.24-r20.1: task do_populate_sysroot_setscene: Started
NOTE: package gnutls-2.10.4-r0: task do_populate_sysroot_setscene: Started
NOTE: package zlib-1.2.5-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package openssl-1.0.0c-r13.2: task do_populate_sysroot_setscene: Succeeded
NOTE: package libnl-1_2.0-r5.0: task do_populate_sysroot_setscene: Started
NOTE: package tcp-wrappers-7.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package tcp-wrappers-7.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gettext-0.17-r5: task do_populate_sysroot_setscene: Started
NOTE: package dbus-1.2.24-r20.1: task do_populate_sysroot_setscene: Succeeded
NOTE: package ncurses-5.9-r0.1: task do_populate_sysroot_setscene: Started
NOTE: package ncurses-5.9-r0.1: task do_populate_sysroot_setscene: Succeeded
NOTE: package gst-plugins-base-0.10.32-r0: task do_populate_sysroot_setscene: Started
NOTE: package libnl-1_2.0-r5.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gnutls-2.10.4-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package alsa-lib-1.0.24.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package libusb-compat-1_0.1.3-r0: task do_populate_sysroot_setscene: Started
NOTE: package libusb-compat-1_0.1.3-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gettext-0.17-r5: task do_populate_sysroot_setscene: Succeeded
NOTE: package dbus-glib-0.92-r0: task do_populate_sysroot_setscene: Started
NOTE: package libpcap-1.1.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package libpcap-1.1.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package elfutils-0.148-r2: task do_populate_sysroot_setscene: Started
NOTE: package dbus-glib-0.92-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package alsa-lib-1.0.24.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package elfutils-0.148-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package update-modules-1.0-r9: task do_populate_sysroot_setscene: Started
NOTE: package module-init-tools-cross-3.12-r1: task do_populate_sysroot_setscene: Started
NOTE: package expat-2.0.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package update-modules-1.0-r9: task do_populate_sysroot_setscene: Succeeded
NOTE: package module-init-tools-cross-3.12-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package libcap-2.20-r0: task do_populate_sysroot_setscene: Started
NOTE: package expat-2.0.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libcap-2.20-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libdaemon-0.14-r0: task do_populate_sysroot_setscene: Started
NOTE: package gtk+-2.20.1-r10.4: task do_populate_sysroot_setscene: Started
NOTE: package libdaemon-0.14-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libglade-2.6.4-r0: task do_populate_sysroot_setscene: Started
NOTE: package libpam-1.1.3-r0: task do_populate_sysroot_setscene: Started
NOTE: package libglade-2.6.4-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package base-passwd-3.5.22-r1: task do_populate_sysroot_setscene: Started
NOTE: package base-passwd-3.5.22-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package busybox-1.18.4-r1: task do_populate_sysroot_setscene: Started
NOTE: package busybox-1.18.4-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package modutils-initscripts-1.0-r5: task do_populate_sysroot_setscene: Started
NOTE: package modutils-initscripts-1.0-r5: task do_populate_sysroot_setscene: Succeeded
NOTE: package bluez-hcidump-2.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package gtk+-2.20.1-r10.4: task do_populate_sysroot_setscene: Succeeded
NOTE: package bluez-hcidump-2.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package python-2.6.6-nk1.3: task do_populate_sysroot_setscene: Started
NOTE: package gst-plugins-base-0.10.32-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package perl-5.12.3-r0: task do_populate_sysroot_setscene: Started
NOTE: package libnss-mdns-0.10-r2: task do_populate_sysroot_setscene: Started
NOTE: package libnss-mdns-0.10-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package psplash-0.0+svnr422-r34: task do_populate_sysroot_setscene: Started
NOTE: package psplash-0.0+svnr422-r34: task do_populate_sysroot_setscene: Succeeded
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_populate_sysroot_setscene: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package gnome-vfs-2.24.4-r0: task do_populate_sysroot_setscene: Started
NOTE: package python-2.6.6-nk1.3: task do_populate_sysroot_setscene: Succeeded
NOTE: package perl-5.12.3-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package hicolor-icon-theme-0.12-r0: task do_populate_sysroot_setscene: Started
NOTE: package hicolor-icon-theme-0.12-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package ttf-dejavu-2.23-r3: task do_populate_sysroot_setscene: Started
NOTE: package ttf-dejavu-2.23-r3: task do_populate_sysroot_setscene: Succeeded
NOTE: package binutils-cross-2.20.1-r5: task do_populate_sysroot_setscene: Started
NOTE: package libgcc-4.5-r0: task do_populate_sysroot_setscene: Started
NOTE: package libpam-1.1.3-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libgcc-4.5-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_populate_sysroot_setscene: Started
NOTE: package lzo-2.05-r0: task do_populate_sysroot_setscene: Started
NOTE: package binutils-cross-2.20.1-r5: task do_populate_sysroot_setscene: Succeeded
NOTE: package attr-2.4.46-r0: task do_populate_sysroot_setscene: Started
NOTE: package attr-2.4.46-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package zip-3.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package lzo-2.05-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package zip-3.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libgpg-error-1.8-r0: task do_populate_sysroot_setscene: Started
NOTE: package libassuan-2.0.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package libgpg-error-1.8-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libassuan-2.0.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gnome-vfs-2.24.4-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package pth-2.0.7-r1: task do_populate_sysroot_setscene: Started
NOTE: package ocf-linux-20100325-r3.0: task do_populate_sysroot_setscene: Started
NOTE: package libtasn1-2.9-r0: task do_populate_sysroot_setscene: Started
NOTE: package ocf-linux-20100325-r3.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libgcrypt-1.4.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package pth-2.0.7-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package libtasn1-2.9-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libsm-1_1.2.0-r1: task do_populate_sysroot_setscene: Started
NOTE: package libice-1_1.0.7-r0: task do_populate_sysroot_setscene: Started
NOTE: package libgcrypt-1.4.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libx11-1_1.4.3-r9.0: task do_populate_sysroot_setscene: Started
NOTE: package libsm-1_1.2.0-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package libice-1_1.0.7-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxdmcp-1_1.1.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package gstreamer-0.10.32-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxdmcp-1_1.1.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package freetype-2.4.4-r0: task do_populate_sysroot_setscene: Started
NOTE: package liboil-0.3.17-r3: task do_populate_sysroot_setscene: Started
NOTE: package liboil-0.3.17-r3: task do_populate_sysroot_setscene: Succeeded
NOTE: package libogg-1.2.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package libx11-1_1.4.3-r9.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package freetype-2.4.4-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libvorbis-1.3.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxv-1.0.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package libogg-1.2.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxv-1.0.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libtheora-1.1.1-r1: task do_populate_sysroot_setscene: Started
NOTE: package libusb1-1.0.8-r0: task do_populate_sysroot_setscene: Started
NOTE: package libvorbis-1.3.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libtheora-1.1.1-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package libusb1-1.0.8-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gstreamer-0.10.32-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libtool-2.4-r2: task do_populate_sysroot_setscene: Started
NOTE: package bzip2-1.0.6-r3: task do_populate_sysroot_setscene: Started
NOTE: package tiff-3.8.2-r2: task do_populate_sysroot_setscene: Started
NOTE: package libtool-2.4-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package pango-1.28.3-r1.0: task do_populate_sysroot_setscene: Started
NOTE: package bzip2-1.0.6-r3: task do_populate_sysroot_setscene: Succeeded
NOTE: package atk-1.30.0-r1: task do_populate_sysroot_setscene: Started
NOTE: package jpeg-8c-r1: task do_populate_sysroot_setscene: Started
NOTE: package tiff-3.8.2-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package atk-1.30.0-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package jpeg-8c-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package libpng-1.2.44-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxext-1_1.2.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxcursor-1_1.1.11-r0: task do_populate_sysroot_setscene: Started
NOTE: package libpng-1.2.44-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxext-1_1.2.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxcursor-1_1.1.11-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gtk-doc-1.0-r4: task do_populate_sysroot_setscene: Started
NOTE: package cups-1.4.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxrandr-1_1.3.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package pango-1.28.3-r1.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gtk-doc-1.0-r4: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxrandr-1_1.3.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxdamage-1_1.1.3-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxrender-1_0.9.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxcomposite-1_0.4.3-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxdamage-1_1.1.3-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package cairo-1.10.0-r1: task do_populate_sysroot_setscene: Started
NOTE: package libxcomposite-1_0.4.3-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package cups-1.4.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxrender-1_0.9.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package jasper-1.900.1-r1: task do_populate_sysroot_setscene: Started
NOTE: package gconf-2.28.0-r2: task do_populate_sysroot_setscene: Started
NOTE: package gnome-common-2.28.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package gnome-common-2.28.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package shared-mime-info-0.90-r0: task do_populate_sysroot_setscene: Started
NOTE: package jasper-1.900.1-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package shared-mime-info-0.90-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gconf-2.28.0-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package bison-2.4.3-r2: task do_populate_sysroot_setscene: Started
NOTE: package cairo-1.10.0-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package flex-2.5.35-r2: task do_populate_sysroot_setscene: Started
NOTE: package bison-2.4.3-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package db-5.1.19-r2: task do_populate_sysroot_setscene: Started
NOTE: package flex-2.5.35-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package gdbm-1.8.3-r4: task do_populate_sysroot_setscene: Started
NOTE: package readline-6.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package sqlite3-3.7.6.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package gdbm-1.8.3-r4: task do_populate_sysroot_setscene: Succeeded
NOTE: package readline-6.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package sqlite3-3.7.6.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxml2-2.7.8-r0: task do_populate_sysroot_setscene: Started
NOTE: package gnome-mime-data-2.18.0-r4: task do_populate_sysroot_setscene: Started
NOTE: package font-update-common-0.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package font-update-common-0.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package xproto-1_7.0.21-r0: task do_populate_sysroot_setscene: Started
NOTE: package xproto-1_7.0.21-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package gnome-mime-data-2.18.0-r4: task do_populate_sysroot_setscene: Succeeded
NOTE: package util-macros-1_1.13.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package eglibc-initial-2.12-r13: task do_populate_sysroot_setscene: Started
NOTE: package util-macros-1_1.13.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxml2-2.7.8-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package xtrans-1_1.2.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package eglibc-initial-2.12-r13: task do_populate_sysroot_setscene: Succeeded
NOTE: package xtrans-1_1.2.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxau-1_1.0.6-r0: task do_populate_sysroot_setscene: Started
NOTE: package bigreqsproto-1_1.1.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package xextproto-1_7.2.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package bigreqsproto-1_1.1.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package xextproto-1_7.2.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxau-1_1.0.6-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package xcmiscproto-1_1.2.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package xf86bigfontproto-1_1.2.0-r1: task do_populate_sysroot_setscene: Started
NOTE: package kbproto-1_1.0.5-r0: task do_populate_sysroot_setscene: Started
NOTE: package db-5.1.19-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package inputproto-1_2.0.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package xf86bigfontproto-1_1.2.0-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package kbproto-1_1.0.5-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package inputproto-1_2.0.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package xcmiscproto-1_1.2.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxcb-1.7-r1: task do_populate_sysroot_setscene: Started
NOTE: package videoproto-1_2.3.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package fontconfig-2.8.0-r1: task do_populate_sysroot_setscene: Started
NOTE: package libxft-1_2.2.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package videoproto-1_2.3.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package fontconfig-2.8.0-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxft-1_2.2.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxfixes-1_5.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package damageproto-1_1.2.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package randrproto-1_1.3.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package libxfixes-1_5.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package damageproto-1_1.2.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package randrproto-1_1.3.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package renderproto-1_0.11.1-r0: task do_populate_sysroot_setscene: Started
NOTE: package compositeproto-1_0.4.2-r0: task do_populate_sysroot_setscene: Started
NOTE: package renderproto-1_0.11.1-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package pixman-0.22.0-r5.0: task do_populate_sysroot_setscene: Started
NOTE: package compositeproto-1_0.4.2-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package orbit2-2.14.17-r0: task do_populate_sysroot_setscene: Started
NOTE: package pixman-0.22.0-r5.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package policykit-0.96-r2: task do_populate_sysroot_setscene: Started
NOTE: package gcc-cross-initial-4.5-r36.0: task do_populate_sysroot_setscene: Started
NOTE: package orbit2-2.14.17-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libxcb-1.7-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: package policykit-0.96-r2: task do_populate_sysroot_setscene: Succeeded
NOTE: package xcb-proto-1.6-r0.0: task do_populate_sysroot_setscene: Started
NOTE: package libpthread-stubs-0.3-r0: task do_populate_sysroot_setscene: Started
NOTE: package fixesproto-1_5.0-r0: task do_populate_sysroot_setscene: Started
NOTE: package xcb-proto-1.6-r0.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libpthread-stubs-0.3-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package fixesproto-1_5.0-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libidl-0.8.13-r0: task do_populate_sysroot_setscene: Started
NOTE: package popt-1.16-r0: task do_populate_sysroot_setscene: Started
NOTE: package eggdbus-0.6-r1: task do_populate_sysroot_setscene: Started
NOTE: package gcc-cross-initial-4.5-r36.0: task do_populate_sysroot_setscene: Succeeded
NOTE: package libidl-0.8.13-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package popt-1.16-r0: task do_populate_sysroot_setscene: Succeeded
NOTE: package eggdbus-0.6-r1: task do_populate_sysroot_setscene: Succeeded
NOTE: Executing RunQueue Tasks
NOTE: Running task 1259 of 3549 (ID: 1746, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_fetch)
NOTE: Running task 1263 of 3549 (ID: 1460, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_fetch)
NOTE: Running task 1273 of 3549 (ID: 1811, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-intermediate_4.5.bb, do_fetch)
NOTE: Running task 1274 of 3549 (ID: 3215, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-initial_4.5.bb, do_fetch)
NOTE: package binutils-cross-2.20.1-r5: task do_fetch: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_fetch: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_fetch: Succeeded
NOTE: package gcc-cross-initial-4.5-r36.0: task do_fetch: Started
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_fetch: Started
NOTE: Running task 1275 of 3549 (ID: 1456, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_unpack)
NOTE: package binutils-cross-2.20.1-r5: task do_fetch: Succeeded
NOTE: Running task 1276 of 3549 (ID: 1742, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_unpack)
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_fetch: Succeeded
NOTE: package gcc-cross-initial-4.5-r36.0: task do_fetch: Succeeded
NOTE: Running task 1277 of 3549 (ID: 1807, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-intermediate_4.5.bb, do_unpack)
NOTE: Running task 1278 of 3549 (ID: 3211, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-initial_4.5.bb, do_unpack)
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_unpack: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_unpack: Started
NOTE: package binutils-cross-2.20.1-r5: task do_unpack: Started
NOTE: package gcc-cross-initial-4.5-r36.0: task do_unpack: Started
NOTE: package binutils-cross-2.20.1-r5: task do_unpack: Succeeded
NOTE: Running task 1279 of 3549 (ID: 1743, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_patch)
NOTE: package binutils-cross-2.20.1-r5: task do_patch: Started
NOTE: package binutils-cross-2.20.1-r5: task do_patch: Succeeded
NOTE: Running task 1280 of 3549 (ID: 1748, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_configure)
NOTE: package binutils-cross-2.20.1-r5: task do_configure: Started
NOTE: package binutils-cross-2.20.1-r5: task do_configure: Succeeded
NOTE: Running task 1281 of 3549 (ID: 1749, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_compile)
NOTE: package binutils-cross-2.20.1-r5: task do_compile: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_unpack: Succeeded
NOTE: Running task 1282 of 3549 (ID: 1753, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_populate_lic)
NOTE: package binutils-cross-2.20.1-r5: task do_populate_lic: Started
NOTE: package binutils-cross-2.20.1-r5: task do_populate_lic: Succeeded
NOTE: Running task 1283 of 3549 (ID: 1457, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_patch)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_patch: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_patch: Succeeded
NOTE: Running task 1284 of 3549 (ID: 1462, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_configure)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_configure: Started
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_unpack: Succeeded
NOTE: Running task 1285 of 3549 (ID: 1467, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_populate_lic)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_populate_lic: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_populate_lic: Succeeded
NOTE: Running task 1286 of 3549 (ID: 1808, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-intermediate_4.5.bb, do_patch)
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_patch: Started
NOTE: package gcc-cross-initial-4.5-r36.0: task do_unpack: Succeeded
NOTE: Running task 1287 of 3549 (ID: 3212, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/gcc/gcc-cross-initial_4.5.bb, do_patch)
NOTE: package gcc-cross-initial-4.5-r36.0: task do_patch: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_configure: Succeeded
NOTE: Running task 1288 of 3549 (ID: 1463, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_compile)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_compile: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_compile: Succeeded
NOTE: Running task 1289 of 3549 (ID: 1458, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_install)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_install: Started
NOTE: package binutils-cross-2.20.1-r5: task do_compile: Succeeded
NOTE: Running task 1290 of 3549 (ID: 1744, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_install)
NOTE: package binutils-cross-2.20.1-r5: task do_install: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_install: Succeeded
NOTE: Running task 1291 of 3549 (ID: 1465, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_package)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_package: Started
NOTE: package binutils-cross-2.20.1-r5: task do_install: Succeeded
NOTE: Running task 1292 of 3549 (ID: 1751, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_package)
NOTE: package binutils-cross-2.20.1-r5: task do_package: Started
NOTE: package binutils-cross-2.20.1-r5: task do_package: Succeeded
NOTE: Running task 1293 of 3549 (ID: 1754, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_package_write_ipk)
NOTE: package binutils-cross-2.20.1-r5: task do_package_write_ipk: Started
NOTE: package binutils-cross-2.20.1-r5: task do_package_write_ipk: Succeeded
NOTE: Running noexec task 1294 of 3549 (ID: 1750, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_package_write)
NOTE: Running noexec task 1295 of 3549 (ID: 1747, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_build)
NOTE: Running task 1296 of 3549 (ID: 1752, /OE/tentacle/sources/meta-openembedded/meta-oe/recipes-devtools/binutils/binutils-cross_2.20.1.bb, do_rm_work)
NOTE: package binutils-cross-2.20.1-r5: task do_rm_work: Started
NOTE: package binutils-cross-2.20.1-r5: task do_rm_work: Succeeded
NOTE: Running task 1297 of 3549 (ID: 2695, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb, do_fetch)
NOTE: package eglibc-initial-2.12-r13: task do_fetch: Started
NOTE: package eglibc-initial-2.12-r13: task do_fetch: Succeeded
NOTE: Running task 1298 of 3549 (ID: 2691, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb, do_unpack)
NOTE: package eglibc-initial-2.12-r13: task do_unpack: Started
NOTE: package eglibc-initial-2.12-r13: task do_unpack: Succeeded
NOTE: Running task 1299 of 3549 (ID: 2692, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb, do_patch)
NOTE: package eglibc-initial-2.12-r13: task do_patch: Started
NOTE: package eglibc-initial-2.12-r13: task do_patch: Succeeded
NOTE: Running task 1300 of 3549 (ID: 2697, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb, do_configure)
NOTE: package eglibc-initial-2.12-r13: task do_configure: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_package: Succeeded
NOTE: Running task 1301 of 3549 (ID: 1468, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_package_write_ipk)
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_package_write_ipk: Started
NOTE: package linux-libc-headers-2.6.37.2-r1: task do_package_write_ipk: Succeeded
NOTE: Running noexec task 1302 of 3549 (ID: 1464, /OE/tentacle/sources/openembedded-core/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_2.6.37.2.bb, do_package_write)
NOTE: Running task 1303 of 3549 (ID: 2702, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb, do_populate_lic)
NOTE: package eglibc-initial-2.12-r13: task do_populate_lic: Started
NOTE: package eglibc-initial-2.12-r13: task do_populate_lic: Succeeded
NOTE: Running task 1304 of 3549 (ID: 823, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc_2.12.bb, do_fetch)
NOTE: package eglibc-2.12-r13: task do_fetch: Started
NOTE: package eglibc-2.12-r13: task do_fetch: Succeeded
NOTE: Running task 1305 of 3549 (ID: 819, /OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc_2.12.bb, do_unpack)
NOTE: package eglibc-2.12-r13: task do_unpack: Started
ERROR: Function 'do_configure' failed (see /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/temp/log.do_configure.23596 for further information)
ERROR: Logfile of failure stored in: /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/temp/log.do_configure.23596
Log data follows:
| + cd /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/build-arm-angstrom-linux-gnueabi
| + do_configure
| + unset CFLAGS
| + sed -e s#@BASH@#/bin/sh# -i /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/elf/ldd.bash.in
| + sed -ie 's,{ (exit 1); exit 1; }; },{ (exit 0); }; },g' /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure
| + chmod +x /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure
| + cd /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc
| + gnu-configize
| + find /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc -name configure
| + xargs touch
| + /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure --host=arm-angstrom-linux-gnueabi --build=x86_64-linux --prefix=/usr --without-cvs --disable-sanity-checks --with-headers=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc/usr/include --enable-hacker-mode --enable-addons
| checking build system type... x86_64-pc-linux-gnu
| checking host system type... arm-angstrom-linux-gnueabi
| checking for arm-angstrom-linux-gnueabi-gcc... ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap
| checking for suffix of object files... configure: error: in `/OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/build-arm-angstrom-linux-gnueabi':
| configure: error: cannot compute suffix of object files: cannot compile
| See `config.log' for more details.
|
| checking whether we are using the GNU C compiler... no
| checking whether ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap accepts -g... no
| checking for ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap option to accept ISO C89... unsupported
| checking for gcc... ccache gcc
| checking how to run the C preprocessor... arm-angstrom-linux-gnueabi-gcc -E --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap
| checking whether we are using the GNU C++ compiler... no
| checking whether ccache arm-angstrom-linux-gnueabi-g++ -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap accepts -g... no
| configure: running configure fragment for add-on libidn
| configure: running configure fragment for add-on nptl
| checking add-on ports for preconfigure fragments... alpha am33 arm hppa m68k mips powerpc
| checking sysdep dirs... checking for assembler gnu_indirect_function symbol type support... no
| ports/sysdeps/arm/elf ports/sysdeps/unix/sysv/linux/arm/eabi/nptl ports/sysdeps/unix/sysv/linux/arm/eabi ports/sysdeps/unix/sysv/linux/arm/nptl ports/sysdeps/unix/sysv/linux/arm nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread ports/sysdeps/unix/sysv/linux sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet nptl/sysdeps/unix/sysv ports/sysdeps/unix/sysv sysdeps/unix/sysv ports/sysdeps/unix/arm nptl/sysdeps/unix ports/sysdeps/unix sysdeps/unix sysdeps/posix ports/sysdeps/arm/eabi ports/sysdeps/arm/fpu ports/sysdeps/arm/nptl ports/sysdeps/arm sysdeps/wordsize-32 sysdeps/ieee754/flt-32 sysdeps/ieee754/dbl-64 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
| checking for a BSD-compatible install... /usr/bin/install -c
| checking whether ln -s works... yes
| checking for arm-angstrom-linux-gnueabi-ranlib... arm-angstrom-linux-gnueabi-ranlib
| checking whether as is GNU as... yes
| checking whether ld is GNU ld... yes
| checking for as... as
| checking version of as... 2.20.1, ok
| checking for ld... ld
| checking version of ld... 2.20.1, ok
| checking for pwd... /bin/pwd
| checking for arm-angstrom-linux-gnueabi-gcc... (cached) ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap
| checking version of ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/OE/tentacle/build/tmp-angstrom_2010_x/sysroots/omap4430-panda-eglibc-tcbootstrap... 4.5.3, ok
| checking for gnumake... make
| checking version of make... 3.81, ok
| checking for gnumsgfmt... no
| checking for gmsgfmt... no
| checking for msgfmt... msgfmt
| checking version of msgfmt... 0.17, ok
| checking for makeinfo... makeinfo
| checking version of makeinfo... 4.13, ok
| checking for sed... sed
| checking version of sed... 4.1.5, ok
| checking for autoconf... autoconf
| checking whether autoconf works... yes
| checking whether ranlib is necessary... Assembler messages:
| Fatal error: Invalid -march= option: `armv7-a'
| ar: conftest.o: No such file or directory
| cp: cannot stat `conftest.a': No such file or directory
| /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure: line 5566: arm-angstrom-linux-gnueabi-ranlib: command not found
| yes
| checking LD_LIBRARY_PATH variable... ok
| checking whether GCC supports -static-libgcc... -static-libgcc
| checking for bash... /bin/bash
| checking for gawk... gawk
| checking for perl... /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/perl
| checking for install-info... /usr/bin/install-info
| checking for bison... /OE/tentacle/build/tmp-angstrom_2010_x/sysroots/x86_64-linux/usr/bin/bison
| checking for signed size_t type... no
| checking for libc-friendly stddef.h... no
| checking whether we need to use -P to assemble .S files... yes
| checking whether .text pseudo-op must be used... no
| checking for assembler global-symbol directive... UNKNOWN
| configure: error: cannot determine asm global directive
| checking for .set assembler directive... no
| checking for assembler .type directive prefix... no
| checking for assembler gnu_unique_object symbol type... no
| checking for .symver assembler directive... no
| checking for ld --version-script... no
| *** WARNING: You should not compile GNU libc without versioning. Not using
| *** versioning will introduce incompatibilities so that old binaries
| *** will not run anymore.
| *** For versioning you need recent binutils (binutils-2.8.1.0.23 or newer).
| checking for .previous assembler directive... no
| checking for .popsection assembler directive... no
| checking for .protected and .hidden assembler directive... configure: error: assembler support for symbol visibility is required
|
| /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure: line 6390: test: =: unary operator expected
| /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure: line 6425: test: =: unary operator expected
| checking for broken __attribute__((alias()))... no
| /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/eglibc-2_12/libc/configure: line 6495: test: =: unary operator expected
| checking for .preinit_array/.init_array/.fini_array support... no
| configure: error: Need linker with .init_array/.fini_array support.
| checking for libunwind-support in compiler... no
| checking for -z nodelete option... configure: error: linker with -z nodelete support required
|
| checking for -z nodlopen option... configure: error: linker with -z nodlopen support required
|
| checkiERROR: Function 'do_configure' failed (see /OE/tentacle/build/tmp-angstrom_2010_x/work/armv7a-angstrom-linux-gnueabi/eglibc-initial-2.12-r13/temp/log.do_configure.23596 for further information)
| ng for -z initfirst option... configure: error: linker with -z initfirst support required
|
| checking for -Bgroup option... no
| checking for libgcc_s suffix...
| checking for --as-needed option... no
| checking whether --noexecstack is desirable for .S files... no
| checking for -z combreloc... no
| checking for -z execstack... no
| checking for --hash-style option... no
| checking for -fno-toplevel-reorder -fno-section-anchors... yes
| checking for -fstack-protector... no
| checking for -fgnu89-inline... yes
| checking whether cc puts quotes around section names... no
| checking for assembler .weak directive... no
| checking for assembler .weakext directive... no
| checking whether CFI directives are supported... no
| checking for ld --no-whole-archive... no
| checking for gcc -fexceptions... no
| checking for __builtin_expect... no
| checking for __builtin_memset... no
| checking for redirection of built-in functions... yes
| checking for __thread... no
| checking for libgd... no
| checking for is_selinux_enabled in -lselinux... no
| checking for grep that handles long lines and -e... /bin/grep
| checking for egrep... /bin/grep -E
| checking for ANSI C header files... no
| checking for sys/types.h... no
| checking for sys/stat.h... no
| checking for stdlib.h... no
| checking for string.h... no
| checking for memory.h... no
| checking for strings.h... no
| checking for inttypes.h... no
| checking for stdint.h... no
| checking for unistd.h... no
| checking size of long double... 0
| running configure fragment for ports/sysdeps/arm/elf
| checking for ARM TLS support... no
| running configure fragment for ports/sysdeps/unix/sysv/linux/arm/eabi/nptl
| running configure fragment for ports/sysdeps/unix/sysv/linux/arm/eabi
| running configure fragment for nptl/sysdeps/pthread
| configure: error: compiler support for __thread is required
NOTE: package eglibc-initial-2.12-r13: task do_configure: Failed
ERROR: Task 2697 (/OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb, do_configure) failed with exit code '1'
Waiting for 3 active tasks to finish:
0: eglibc-2.12-r13 do_unpack (pid 26022)
1: gcc-cross-intermediate-4.5-r36.0 do_patch (pid 27335)
2: gcc-cross-initial-4.5-r36.0 do_patch (pid 32188)
Waiting for 2 active tasks to finish:
0: gcc-cross-intermediate-4.5-r36.0 do_patch (pid 27335)
1: gcc-cross-initial-4.5-r36.0 do_patch (pid 32188)
NOTE: package eglibc-2.12-r13: task do_unpack: Succeeded
Waiting for 1 active tasks to finish:
0: gcc-cross-intermediate-4.5-r36.0 do_patch (pid 27335)
NOTE: package gcc-cross-initial-4.5-r36.0: task do_patch: Succeeded
NOTE: package gcc-cross-intermediate-4.5-r36.0: task do_patch: Succeeded
ERROR: '/OE/tentacle/sources/openembedded-core/meta/recipes-core/eglibc/eglibc-initial_2.12.bb' failed
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-16 11:20 sstate breakage with multimachine Koen Kooi
@ 2011-05-16 23:13 ` Richard Purdie
2011-05-17 6:34 ` Koen Kooi
2011-05-17 7:14 ` Martin Jansa
1 sibling, 1 reply; 9+ messages in thread
From: Richard Purdie @ 2011-05-16 23:13 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Mon, 2011-05-16 at 13:20 +0200, Koen Kooi wrote:
> This bug gets reintroduced every other week, so let's try to fix it
> properly this time. The situation:
>
> 2 machines (beagleboard, pandaboard) using the same base architecture
> (armv7a).
>
> step 0: rm build pseudone -rf
> step 1: MACHINE=beagleboard bitbake console-image
> step 2: MACHINE=omap4430-panda bitbake console-image
>
> Step 0 and 1 work great, but I can't get step 2 to work. Attached is
> the complete output of step 2. As you can see without any updates to
> the repositories it wants to rebuild (e)glibc.
>
> Why does it wants to rebuild all that? Why does it fail?
I had a look at this. Firstly, I figured out I needed an incantation to
reproduce which turned out to be:
git clone git://git.angstrom-distribution.org/setup-scripts
git checkout oe-core
MACHINE=beagleboard ./oebb.sh config beagleboard
MACHINE=beagleboard ./oebb.sh bitbake console-image -S
MACHINE=omap4430-panda ./oebb.sh bitbake console-image -S
I added the -S option to dump sigdata files into the stamp directory so
I didn't need to run two builds before being able to look at this. Sure
enough, if you look
at /media/build2/builds/angstrom/setup-scripts/build/tmp-angstrom_2010_x/stamps/all-angstrom-linux-gnueabi
update-rc.d* then the do_populate_lic task is duplicated as are the
do_package and its subsequent tasks.
Diffing the do_populate_lic task, it shows DEPLOY_DIR_IMAGE has a
dependency on the MACHINE variable so its correctly rerunning the task
for that reason. This is an Angstrom specific change and adding:
DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
+DEPLOY_DIR_IMAGE[vardepsexclude] = "MACHINE"
to conf/distro/include/angstrom.inc makes it go away. I'm not claiming
its the correct fix, it just proves where the problem is.
Secondly, the do_package task was depending on eglibc do_package. This
is almost certainly due to the default dependencies on things like
virtual/libc which we add. Being an "all" PACKAGE_ARCH, it clearly
doesn't depend on this so adding INHIBIT_DEFAULT_DEPS = "1" to the
update-rc.d recipe removed that problem and meant packaging didn't
rerun.
Further investigation is needed and these fixes need some thought and
creation of proper patches but hopefully this gives a handle on whats
going on and it turns out its not that hard to figure out (although some
scripts to compare two such runs would be interesting and/or some proper
test cases).
Note that the DEPLOY_DIR_IMAGE[vardepsexclude] is not correct. The
do_populate_lic task is putting files into the directory and the system
is therefore totally correct in deciding that the task needed to rerun
as the files were being placed in a different directory. do_populate_lic
could likely use some work in that regard as I'm not sure this is the
right place to be putting its data though.
Cheers,
Richard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-16 23:13 ` Richard Purdie
@ 2011-05-17 6:34 ` Koen Kooi
2011-05-17 9:37 ` Richard Purdie
0 siblings, 1 reply; 9+ messages in thread
From: Koen Kooi @ 2011-05-17 6:34 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Op 17 mei 2011, om 01:13 heeft Richard Purdie het volgende geschreven:
> On Mon, 2011-05-16 at 13:20 +0200, Koen Kooi wrote:
>> This bug gets reintroduced every other week, so let's try to fix it
>> properly this time. The situation:
>>
>> 2 machines (beagleboard, pandaboard) using the same base architecture
>> (armv7a).
>>
>> step 0: rm build pseudone -rf
>> step 1: MACHINE=beagleboard bitbake console-image
>> step 2: MACHINE=omap4430-panda bitbake console-image
>>
>> Step 0 and 1 work great, but I can't get step 2 to work. Attached is
>> the complete output of step 2. As you can see without any updates to
>> the repositories it wants to rebuild (e)glibc.
>>
>> Why does it wants to rebuild all that? Why does it fail?
>
> I had a look at this. Firstly, I figured out I needed an incantation to
> reproduce which turned out to be:
>
> git clone git://git.angstrom-distribution.org/setup-scripts
> git checkout oe-core
> MACHINE=beagleboard ./oebb.sh config beagleboard
> MACHINE=beagleboard ./oebb.sh bitbake console-image -S
> MACHINE=omap4430-panda ./oebb.sh bitbake console-image -S
>
> I added the -S option to dump sigdata files into the stamp directory so
> I didn't need to run two builds before being able to look at this. Sure
> enough, if you look
> at /media/build2/builds/angstrom/setup-scripts/build/tmp-angstrom_2010_x/stamps/all-angstrom-linux-gnueabi
> update-rc.d* then the do_populate_lic task is duplicated as are the
> do_package and its subsequent tasks.
>
> Diffing the do_populate_lic task, it shows DEPLOY_DIR_IMAGE has a
> dependency on the MACHINE variable so its correctly rerunning the task
> for that reason. This is an Angstrom specific change and adding:
>
> DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
> +DEPLOY_DIR_IMAGE[vardepsexclude] = "MACHINE"
>
> to conf/distro/include/angstrom.inc makes it go away. I'm not claiming
> its the correct fix, it just proves where the problem is.
>
> Secondly, the do_package task was depending on eglibc do_package. This
> is almost certainly due to the default dependencies on things like
> virtual/libc which we add. Being an "all" PACKAGE_ARCH, it clearly
> doesn't depend on this so adding INHIBIT_DEFAULT_DEPS = "1" to the
> update-rc.d recipe removed that problem and meant packaging didn't
> rerun.
>
> Further investigation is needed and these fixes need some thought and
> creation of proper patches but hopefully this gives a handle on whats
> going on and it turns out its not that hard to figure out (although some
> scripts to compare two such runs would be interesting and/or some proper
> test cases).
>
> Note that the DEPLOY_DIR_IMAGE[vardepsexclude] is not correct. The
> do_populate_lic task is putting files into the directory and the system
> is therefore totally correct in deciding that the task needed to rerun
> as the files were being placed in a different directory. do_populate_lic
> could likely use some work in that regard as I'm not sure this is the
> right place to be putting its data though.
Thanks for looking into this! For the time being I'll work around it with:
oen@dominion:/OE/tentacle/sources/meta-angstrom$ git diff conf/distro/
diff --git a/conf/distro/include/angstrom-core-tweaks.inc b/conf/distro/include/angstrom-core-tweaks.inc
index e4bd798..fe9225c 100644
--- a/conf/distro/include/angstrom-core-tweaks.inc
+++ b/conf/distro/include/angstrom-core-tweaks.inc
@@ -18,6 +18,11 @@ STAGING_DIR_HOST = "${STAGING_DIR}/${MACHINE}-${TCLIBC}"
+# Work around multimachine breakage
+# See http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/002535.html
+
+LICENSE_DIRECTORY = "${DEPLOY_DIR}/licenses"
I think that's a better place to stash those licenses, since we drop images in DEPLOY/image, sources in DEPLOY/sources and sdks in DEPLOY/sdk so DEPLOY/licenses makes sense.
Do you want me to send a patch to license.bbclass for this?
regards,
Koen
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-16 11:20 sstate breakage with multimachine Koen Kooi
2011-05-16 23:13 ` Richard Purdie
@ 2011-05-17 7:14 ` Martin Jansa
2011-05-17 9:42 ` Richard Purdie
1 sibling, 1 reply; 9+ messages in thread
From: Martin Jansa @ 2011-05-17 7:14 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]
On Mon, May 16, 2011 at 01:20:02PM +0200, Koen Kooi wrote:
> Hi,
>
> This bug gets reintroduced every other week, so let's try to fix it properly this time. The situation:
>
> 2 machines (beagleboard, pandaboard) using the same base architecture (armv7a).
>
> step 0: rm build pseudone -rf
> step 1: MACHINE=beagleboard bitbake console-image
> step 2: MACHINE=omap4430-panda bitbake console-image
>
> Step 0 and 1 work great, but I can't get step 2 to work. Attached is the complete output of step 2. As you can see without any updates to the repositories it wants to rebuild (e)glibc.
>
> Why does it wants to rebuild all that? Why does it fail?
>
> regards,
>
> Koen
Hi,
there is also another source of many sstate rebuilds. I've discuessed
this with RP on IRC already and I'll fill bugs as recommended, sharing
here just because you have opened this topic.
If you have package with
PACKAGE_ARCH = "all"
then the resulting package is created by run.* scripts with different
pathsi, *FLAGS etc even when it produces same output (ie some theme).
So all packages with such PACKAGE_ARCH are rebuilt after machine switch
(if the machine is ie different arch like om-gta02/nokia900).
Sstate is reused when you go back to om-gta02 after building nokia900,
so you have ie populate_sysroot only with as many checksums as you're
building different archs.
RP said, that right fix is to introduce something like all.bbclass which
excludes all variables which shouldn't change the output of such package
and then checksums will be the same.
Here is example with gtk-theme-e17lookalike http://paste.pocoo.org/show/388032/
And as side-note there is small problem when someone tries to hunt such
checksum changes, because some tasks which are not directly using sstate
like do_install do not save their run.* scripts in better place then
${WORKDIR}/temp
So if your bitbake-diffsigs shows something like this:
Hash for dependent task
/OE/shr-core/meta-shr/recipes-shr/shr/gtk-theme-e17lookalike_git.bb.do_install
changed from 8a0de44f3f238f645eab9509172c2d8b to
9d6bf027c5f435498017a652088d7327
You need to find right ${WORKDIR} for that version, and there in temp
directory right combination of run.do_install._pid_ scripts, but you
don't know which _pid_ belongs to which sstate checksum and I guess pid
cannot be stored in .siginfo because it would be always different.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-17 6:34 ` Koen Kooi
@ 2011-05-17 9:37 ` Richard Purdie
0 siblings, 0 replies; 9+ messages in thread
From: Richard Purdie @ 2011-05-17 9:37 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Tue, 2011-05-17 at 08:34 +0200, Koen Kooi wrote:
> Thanks for looking into this! For the time being I'll work around it with:
>
> oen@dominion:/OE/tentacle/sources/meta-angstrom$ git diff conf/distro/
> diff --git a/conf/distro/include/angstrom-core-tweaks.inc b/conf/distro/include/angstrom-core-tweaks.inc
> index e4bd798..fe9225c 100644
> --- a/conf/distro/include/angstrom-core-tweaks.inc
> +++ b/conf/distro/include/angstrom-core-tweaks.inc
> @@ -18,6 +18,11 @@ STAGING_DIR_HOST = "${STAGING_DIR}/${MACHINE}-${TCLIBC}"
> +# Work around multimachine breakage
> +# See http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/002535.html
> +
> +LICENSE_DIRECTORY = "${DEPLOY_DIR}/licenses"
>
> I think that's a better place to stash those licenses, since we drop images in DEPLOY/image, sources in DEPLOY/sources and sdks in DEPLOY/sdk so DEPLOY/licenses makes sense.
>
> Do you want me to send a patch to license.bbclass for this?
Yes please.
Cheers,
Richard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-17 7:14 ` Martin Jansa
@ 2011-05-17 9:42 ` Richard Purdie
2011-05-17 11:37 ` Martin Jansa
0 siblings, 1 reply; 9+ messages in thread
From: Richard Purdie @ 2011-05-17 9:42 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Tue, 2011-05-17 at 09:14 +0200, Martin Jansa wrote:
> there is also another source of many sstate rebuilds. I've discuessed
> this with RP on IRC already and I'll fill bugs as recommended, sharing
> here just because you have opened this topic.
>
> If you have package with
> PACKAGE_ARCH = "all"
> then the resulting package is created by run.* scripts with different
> pathsi, *FLAGS etc even when it produces same output (ie some theme).
>
> So all packages with such PACKAGE_ARCH are rebuilt after machine switch
> (if the machine is ie different arch like om-gta02/nokia900).
> Sstate is reused when you go back to om-gta02 after building nokia900,
> so you have ie populate_sysroot only with as many checksums as you're
> building different archs.
>
> RP said, that right fix is to introduce something like all.bbclass which
> excludes all variables which shouldn't change the output of such package
> and then checksums will be the same.
I think rather then exclude them, we should zero them out or unexport
them and stop them being present in the task environment. We should file
a bug about this problem in the Yocto bugzilla.
> Here is example with gtk-theme-e17lookalike http://paste.pocoo.org/show/388032/
>
> And as side-note there is small problem when someone tries to hunt such
> checksum changes, because some tasks which are not directly using sstate
> like do_install do not save their run.* scripts in better place then
> ${WORKDIR}/temp
>
> So if your bitbake-diffsigs shows something like this:
>
> Hash for dependent task
> /OE/shr-core/meta-shr/recipes-shr/shr/gtk-theme-e17lookalike_git.bb.do_install
> changed from 8a0de44f3f238f645eab9509172c2d8b to
> 9d6bf027c5f435498017a652088d7327
>
> You need to find right ${WORKDIR} for that version, and there in temp
> directory right combination of run.do_install._pid_ scripts, but you
> don't know which _pid_ belongs to which sstate checksum and I guess pid
> cannot be stored in .siginfo because it would be always different.
Just for reference, if you want to generate two trees of all tasks
sigdata to compare you can do something like:
MACHINE=qemuarm bitbake console-image -S
MACHINE=qemux86 bitbake console-image -S
and then look at the tmpdir/stamps/*/* files using bitbake-diffsigs on
the files there to try and do this comparison more directly.
I'm open to other ideas to improving the way we write out the sigdata
pieces to make this kind of analysis easier...
Cheers,
Richard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-17 9:42 ` Richard Purdie
@ 2011-05-17 11:37 ` Martin Jansa
2011-05-17 23:10 ` Richard Purdie
0 siblings, 1 reply; 9+ messages in thread
From: Martin Jansa @ 2011-05-17 11:37 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 4000 bytes --]
On Tue, May 17, 2011 at 10:42:52AM +0100, Richard Purdie wrote:
> On Tue, 2011-05-17 at 09:14 +0200, Martin Jansa wrote:
> > there is also another source of many sstate rebuilds. I've discuessed
> > this with RP on IRC already and I'll fill bugs as recommended, sharing
> > here just because you have opened this topic.
> >
> > If you have package with
> > PACKAGE_ARCH = "all"
> > then the resulting package is created by run.* scripts with different
> > pathsi, *FLAGS etc even when it produces same output (ie some theme).
> >
> > So all packages with such PACKAGE_ARCH are rebuilt after machine switch
> > (if the machine is ie different arch like om-gta02/nokia900).
> > Sstate is reused when you go back to om-gta02 after building nokia900,
> > so you have ie populate_sysroot only with as many checksums as you're
> > building different archs.
> >
> > RP said, that right fix is to introduce something like all.bbclass which
> > excludes all variables which shouldn't change the output of such package
> > and then checksums will be the same.
>
> I think rather then exclude them, we should zero them out or unexport
> them and stop them being present in the task environment. We should file
> a bug about this problem in the Yocto bugzilla.
Already did in morning
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1075
>
> > Here is example with gtk-theme-e17lookalike http://paste.pocoo.org/show/388032/
> >
> > And as side-note there is small problem when someone tries to hunt such
> > checksum changes, because some tasks which are not directly using sstate
> > like do_install do not save their run.* scripts in better place then
> > ${WORKDIR}/temp
> >
> > So if your bitbake-diffsigs shows something like this:
> >
> > Hash for dependent task
> > /OE/shr-core/meta-shr/recipes-shr/shr/gtk-theme-e17lookalike_git.bb.do_install
> > changed from 8a0de44f3f238f645eab9509172c2d8b to
> > 9d6bf027c5f435498017a652088d7327
> >
> > You need to find right ${WORKDIR} for that version, and there in temp
> > directory right combination of run.do_install._pid_ scripts, but you
> > don't know which _pid_ belongs to which sstate checksum and I guess pid
> > cannot be stored in .siginfo because it would be always different.
>
> Just for reference, if you want to generate two trees of all tasks
> sigdata to compare you can do something like:
>
> MACHINE=qemuarm bitbake console-image -S
> MACHINE=qemux86 bitbake console-image -S
>
> and then look at the tmpdir/stamps/*/* files using bitbake-diffsigs on
> the files there to try and do this comparison more directly.
This works for multimachine build when I'm trying to find what's
different between qemuarm and qemux86, but wont help if I'm trying to
find what's changed in run.do_install from last week when I notice that
some package is being rebuilt again.
Also already in bugzilla
http://bugzilla.yoctoproject.org/show_bug.cgi?id=1074
> I'm open to other ideas to improving the way we write out the sigdata
> pieces to make this kind of analysis easier...
I don't know sstate internals as you do, but cannot we store every
dependant task used to count checksum in something like
state-gtk-theme-e17lookalike-all-oe-linux-gnueabi-0.1.1+gitr3+9b92a3d095ef1b53f55026cc292771d1507e6800-r8-all-2-do_install_8a0de44f3f238f645eab9509172c2d8b.gz
and from second run
state-gtk-theme-e17lookalike-all-oe-linux-gnueabi-0.1.1+gitr3+9b92a3d095ef1b53f55026cc292771d1507e6800-r8-all-2-do_install_9d6bf027c5f435498017a652088d7327.gz
or even flat filename structure like
siginfo-do_install_8a0de44f3f238f645eab9509172c2d8b.gz and
siginfo-do_install_9d6bf027c5f435498017a652088d7327.gz
as hash collision is not very likely to happen and overwrites with same
script are ok.
Then it would be easy to find actuall scripts which caused checksum
change without ${WORKDIR}/temp files
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-17 11:37 ` Martin Jansa
@ 2011-05-17 23:10 ` Richard Purdie
2011-05-18 4:26 ` Martin Jansa
0 siblings, 1 reply; 9+ messages in thread
From: Richard Purdie @ 2011-05-17 23:10 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Tue, 2011-05-17 at 13:37 +0200, Martin Jansa wrote:
> On Tue, May 17, 2011 at 10:42:52AM +0100, Richard Purdie wrote:
> > On Tue, 2011-05-17 at 09:14 +0200, Martin Jansa wrote:
> > > there is also another source of many sstate rebuilds. I've discuessed
> > > this with RP on IRC already and I'll fill bugs as recommended, sharing
> > > here just because you have opened this topic.
> > >
> > > If you have package with
> > > PACKAGE_ARCH = "all"
> > > then the resulting package is created by run.* scripts with different
> > > pathsi, *FLAGS etc even when it produces same output (ie some theme).
> > >
> > > So all packages with such PACKAGE_ARCH are rebuilt after machine switch
> > > (if the machine is ie different arch like om-gta02/nokia900).
> > > Sstate is reused when you go back to om-gta02 after building nokia900,
> > > so you have ie populate_sysroot only with as many checksums as you're
> > > building different archs.
> > >
> > > RP said, that right fix is to introduce something like all.bbclass which
> > > excludes all variables which shouldn't change the output of such package
> > > and then checksums will be the same.
> >
> > I think rather then exclude them, we should zero them out or unexport
> > them and stop them being present in the task environment. We should file
> > a bug about this problem in the Yocto bugzilla.
>
> Already did in morning
> http://bugzilla.yoctoproject.org/show_bug.cgi?id=1075
Its not finished but here is a start at this:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/allarch&id=0944f7393054a91ce1508ec1a98bd4c612ee90e4
I fixed up encodings to compile (without trying to us a compiler). The
same kind of fixes are needed for gnome-icon-theme, font-alias and
possibly others. If they are truly "all" arch, they shouldn't be trying
to access a compiler at all.
> > > Here is example with gtk-theme-e17lookalike http://paste.pocoo.org/show/388032/
> > >
> > > And as side-note there is small problem when someone tries to hunt such
> > > checksum changes, because some tasks which are not directly using sstate
> > > like do_install do not save their run.* scripts in better place then
> > > ${WORKDIR}/temp
> > >
> > > So if your bitbake-diffsigs shows something like this:
> > >
> > > Hash for dependent task
> > > /OE/shr-core/meta-shr/recipes-shr/shr/gtk-theme-e17lookalike_git.bb.do_install
> > > changed from 8a0de44f3f238f645eab9509172c2d8b to
> > > 9d6bf027c5f435498017a652088d7327
> > >
> > > You need to find right ${WORKDIR} for that version, and there in temp
> > > directory right combination of run.do_install._pid_ scripts, but you
> > > don't know which _pid_ belongs to which sstate checksum and I guess pid
> > > cannot be stored in .siginfo because it would be always different.
> >
> > Just for reference, if you want to generate two trees of all tasks
> > sigdata to compare you can do something like:
> >
> > MACHINE=qemuarm bitbake console-image -S
> > MACHINE=qemux86 bitbake console-image -S
> >
> > and then look at the tmpdir/stamps/*/* files using bitbake-diffsigs on
> > the files there to try and do this comparison more directly.
>
> This works for multimachine build when I'm trying to find what's
> different between qemuarm and qemux86, but wont help if I'm trying to
> find what's changed in run.do_install from last week when I notice that
> some package is being rebuilt again.
>
> Also already in bugzilla
> http://bugzilla.yoctoproject.org/show_bug.cgi?id=1074
>
> > I'm open to other ideas to improving the way we write out the sigdata
> > pieces to make this kind of analysis easier...
>
> I don't know sstate internals as you do, but cannot we store every
> dependant task used to count checksum in something like
> state-gtk-theme-e17lookalike-all-oe-linux-gnueabi-0.1.1+gitr3+9b92a3d095ef1b53f55026cc292771d1507e6800-r8-all-2-do_install_8a0de44f3f238f645eab9509172c2d8b.gz
> and from second run
> state-gtk-theme-e17lookalike-all-oe-linux-gnueabi-0.1.1+gitr3+9b92a3d095ef1b53f55026cc292771d1507e6800-r8-all-2-do_install_9d6bf027c5f435498017a652088d7327.gz
>
> or even flat filename structure like
> siginfo-do_install_8a0de44f3f238f645eab9509172c2d8b.gz and
> siginfo-do_install_9d6bf027c5f435498017a652088d7327.gz
> as hash collision is not very likely to happen and overwrites with same
> script are ok.
>
> Then it would be easy to find actuall scripts which caused checksum
> change without ${WORKDIR}/temp files
How about:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/allarch&id=aca23a2ab92ad950d44dd45524773591bc7993bc
which results in sigdata files in the stamp directory.
Cheers,
Richard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sstate breakage with multimachine
2011-05-17 23:10 ` Richard Purdie
@ 2011-05-18 4:26 ` Martin Jansa
0 siblings, 0 replies; 9+ messages in thread
From: Martin Jansa @ 2011-05-18 4:26 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 5527 bytes --]
On Wed, May 18, 2011 at 12:10:42AM +0100, Richard Purdie wrote:
> On Tue, 2011-05-17 at 13:37 +0200, Martin Jansa wrote:
> > On Tue, May 17, 2011 at 10:42:52AM +0100, Richard Purdie wrote:
> > > On Tue, 2011-05-17 at 09:14 +0200, Martin Jansa wrote:
> > > > there is also another source of many sstate rebuilds. I've discuessed
> > > > this with RP on IRC already and I'll fill bugs as recommended, sharing
> > > > here just because you have opened this topic.
> > > >
> > > > If you have package with
> > > > PACKAGE_ARCH = "all"
> > > > then the resulting package is created by run.* scripts with different
> > > > pathsi, *FLAGS etc even when it produces same output (ie some theme).
> > > >
> > > > So all packages with such PACKAGE_ARCH are rebuilt after machine switch
> > > > (if the machine is ie different arch like om-gta02/nokia900).
> > > > Sstate is reused when you go back to om-gta02 after building nokia900,
> > > > so you have ie populate_sysroot only with as many checksums as you're
> > > > building different archs.
> > > >
> > > > RP said, that right fix is to introduce something like all.bbclass which
> > > > excludes all variables which shouldn't change the output of such package
> > > > and then checksums will be the same.
> > >
> > > I think rather then exclude them, we should zero them out or unexport
> > > them and stop them being present in the task environment. We should file
> > > a bug about this problem in the Yocto bugzilla.
> >
> > Already did in morning
> > http://bugzilla.yoctoproject.org/show_bug.cgi?id=1075
>
> Its not finished but here is a start at this:
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/allarch&id=0944f7393054a91ce1508ec1a98bd4c612ee90e4
just nitpick in meta/recipes-bsp/hostap/hostap-conf_1.0.bb
-PR = "r12"
+PR = "r142"
but I'll use test allarch when my current build finishes and let you
know, The same for 2nd patch.
Thanks!
Cheers,
> I fixed up encodings to compile (without trying to us a compiler). The
> same kind of fixes are needed for gnome-icon-theme, font-alias and
> possibly others. If they are truly "all" arch, they shouldn't be trying
> to access a compiler at all.
>
>
> > > > Here is example with gtk-theme-e17lookalike http://paste.pocoo.org/show/388032/
> > > >
> > > > And as side-note there is small problem when someone tries to hunt such
> > > > checksum changes, because some tasks which are not directly using sstate
> > > > like do_install do not save their run.* scripts in better place then
> > > > ${WORKDIR}/temp
> > > >
> > > > So if your bitbake-diffsigs shows something like this:
> > > >
> > > > Hash for dependent task
> > > > /OE/shr-core/meta-shr/recipes-shr/shr/gtk-theme-e17lookalike_git.bb.do_install
> > > > changed from 8a0de44f3f238f645eab9509172c2d8b to
> > > > 9d6bf027c5f435498017a652088d7327
> > > >
> > > > You need to find right ${WORKDIR} for that version, and there in temp
> > > > directory right combination of run.do_install._pid_ scripts, but you
> > > > don't know which _pid_ belongs to which sstate checksum and I guess pid
> > > > cannot be stored in .siginfo because it would be always different.
> > >
> > > Just for reference, if you want to generate two trees of all tasks
> > > sigdata to compare you can do something like:
> > >
> > > MACHINE=qemuarm bitbake console-image -S
> > > MACHINE=qemux86 bitbake console-image -S
> > >
> > > and then look at the tmpdir/stamps/*/* files using bitbake-diffsigs on
> > > the files there to try and do this comparison more directly.
> >
> > This works for multimachine build when I'm trying to find what's
> > different between qemuarm and qemux86, but wont help if I'm trying to
> > find what's changed in run.do_install from last week when I notice that
> > some package is being rebuilt again.
> >
> > Also already in bugzilla
> > http://bugzilla.yoctoproject.org/show_bug.cgi?id=1074
> >
> > > I'm open to other ideas to improving the way we write out the sigdata
> > > pieces to make this kind of analysis easier...
> >
> > I don't know sstate internals as you do, but cannot we store every
> > dependant task used to count checksum in something like
> > state-gtk-theme-e17lookalike-all-oe-linux-gnueabi-0.1.1+gitr3+9b92a3d095ef1b53f55026cc292771d1507e6800-r8-all-2-do_install_8a0de44f3f238f645eab9509172c2d8b.gz
> > and from second run
> > state-gtk-theme-e17lookalike-all-oe-linux-gnueabi-0.1.1+gitr3+9b92a3d095ef1b53f55026cc292771d1507e6800-r8-all-2-do_install_9d6bf027c5f435498017a652088d7327.gz
> >
> > or even flat filename structure like
> > siginfo-do_install_8a0de44f3f238f645eab9509172c2d8b.gz and
> > siginfo-do_install_9d6bf027c5f435498017a652088d7327.gz
> > as hash collision is not very likely to happen and overwrites with same
> > script are ok.
> >
> > Then it would be easy to find actuall scripts which caused checksum
> > change without ${WORKDIR}/temp files
>
> How about:
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/allarch&id=aca23a2ab92ad950d44dd45524773591bc7993bc
>
> which results in sigdata files in the stamp directory.
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-05-18 4:36 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-16 11:20 sstate breakage with multimachine Koen Kooi
2011-05-16 23:13 ` Richard Purdie
2011-05-17 6:34 ` Koen Kooi
2011-05-17 9:37 ` Richard Purdie
2011-05-17 7:14 ` Martin Jansa
2011-05-17 9:42 ` Richard Purdie
2011-05-17 11:37 ` Martin Jansa
2011-05-17 23:10 ` Richard Purdie
2011-05-18 4:26 ` Martin Jansa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox