Hi,
FWIW: I have been seeing what appears to be an identical problem when trying to build systemd-image or console-image for the last day or so. Target machine is beaglebone and build system is Ubuntu 11.10. The problem is reproducible when rerunning the systemd-image.bb do_rootfs task alone. cooker.log: NOTE: Running noexec task 10 of 13 (ID: 9, /home/mark/dev/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/systemd-image.bb, do_package_write) NOTE: Running task 11 of 13 (ID: 8, /home/mark/dev/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/systemd-image.bb, do_rootfs) NOTE: package systemd-image-1.0-r0: task do_rootfs: Started ERROR: Function failed: do_rootfs (see /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-image-1.0-r0/temp/log.do_rootfs.24289 for further information) NOTE: package systemd-image-1.0-r0: task do_rootfs: Failed ERROR: Task 8 (/home/mark/dev/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/systemd-image.bb, do_rootfs) failed with exit code '1' The aforementioned log file shows a similar non-graceful exit: + opkg-cl -f /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-image-1.0-r0/opkg.conf -o /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-image-1.0-r0/rootfs --force-overwrite info shadow + info=Package: shadow Version: 4.1.4.3-r8 Depends: libpam-runtime, pam-plugin-env, shadow-securetty, pam-plugin-faildelay, pam-plugin-securetty, pam-plugin-limits, pam-plugin-nologin, pam-plugin-motd, pam-plugin-shells, pam-plugin-group, pam-plugin-mail, libc6 (>= 2.12), pam-plugin-rootok, libpam (>= 1.1.5), pam-plugin-lastlog Provides: Status: install user installed Section: base utils Architecture: armv7a Maintainer: Angstrom Developers <angstrom-distro-devel@linuxtogo.org> -- Size: 363136 Filename: shadow_4.1.4.3-r8_armv7a.ipk Source: http://pkg-shadow.alioth.debian.org/releases/shadow-4.1.4.3.tar.bz2 file://login_defs_pam.sed file://pam.d/chfn file://pam.d/chpasswd file://pam.d/chsh file://pam.d/login file://pam.d/newusers file://pam.ERROR: Function failed: do_rootfs (see /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-image-1.0-r0/temp/log.do_rootfs.24289 for further information) d/passwd file://pam.d/su file://shadow.automake-1.11.patch file://shadow-4.1.3-dots-in-usernames.patch file://shadow-4.1.4.2-env-reset-keep-locale.patch file://shadow-4.1.4.2-groupmod-pam-check.patch file://shadow-4.1.4.2-su_no_sanitize_env.patch file://shadow-update-pam-conf.patch + echo Package: shadow Version: 4.1.4.3-r8 The following excerpt from qa.log may or may not be relevant. consolekit-0.4.5: consolekit: /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/consolekit-0.4.5-r9/packages-split/pam-plugin-ck-connector/lib/security/pam_ck_connector.so links to something under exec_prefix consolekit-0.4.5: ldd reports: libpam.so.0 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/lib/libpam.so.0 (0xdead1000) libdl.so.2 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/lib/libdl.so.2 (0xdead2000) libck-connector.so.0 => not found libdbus-1.so.3 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/usr/lib/libdbus-1.so.3 (0xdead3000) libpthread.so.0 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/lib/libpthread.so.0 (0xdead4000) librt.so.1 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/lib/librt.so.1 (0xdead5000) libc.so.6 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/lib/libc.so.6 (0xdead6000) /lib/ld-linux.so.3 => /home/mark/dev/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/lib/ld-linux.so.3 (0xdead7000) I'm afraid I've got nothing more helpful on this. Thanks, Mark ________________________________ From: Russell Senior <russ...@personaltelco.net> To: angstrom-distro-devel@linuxtogo.org Sent: Wednesday, 28 March 2012, 13:07 Subject: [Angstrom-devel] clean systemd-image build failing with non-zero exit ... ... and no effing clue what exited, except it was part of do_rootfs. The error message is emitted in the middle of another message relating to some pam modules, but it is not at all obvious that the error is related to pam at all. The error message points at the log file, but the log file gives no clue what went wrong. The messages that get interrupted seem to be related to the .dot file creation, but the .dot file appears complete in the aftermath. http://www.tdb.com/~russell/log.do_rootfs.txt wtf? This was on an up-to-date angstrom checkout and update as of last night, compiling for beaglebone. MACHINE=beaglebone bitbake systemd-image -- Russell Senior, President russ...@personaltelco.net _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
