On Tue, Mar 27, 2012 at 10:07:54PM -0700, Russell Senior wrote: > > ... 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
Can you retry with buildhistory disabled? I had similar issue and log when doing http://git.openembedded.org/openembedded-core/commit/?id=9a8199e4a0f46ed3e9582143b206144aee28b709 but with || true and quotes it worked for me (and produced the same buildhistory output), but maybe there is some corner case not covered by this (mine was triggered by BAD_RECOMMENDATIONS)? Cheers, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
