When issues arise, a log of the bitbake output is often helpful (not just the logs under the package temp directories). Users don't typically do this, and for hard to reproduce bugs, regenerating a log may not be doable. I'm using the following script, which I posted to the mailing list here: https://lists.yoctoproject.org/pipermail/yocto/2011-November/005527.html where it received some discussion. It seems this sort of thing may generally useful. #!/bin/bash TIMESTAMP=$(date -u "+%Y%m%d%H%M%S") LOG=$(mktemp --suffix=".log" bb-$TIMESTAMP-XXX) if [ -z "$LOG" ]; then echo "ERROR: failed to create log file" exit 1 fi ( echo "Start: $TIMESTAMP" echo "========================================" /usr/bin/time 2>&1 -v bitbake $@ echo "========================================" echo "End: $(date -u '+%Y%m%d%H%M%S')" ) | tee $LOG echo "Logfile: $LOG"
I think given the log handling code we have in bitbake, we should just mirror the console output to a logfile somewhere in TMPDIR automatically...
(In reply to comment #1) > I think given the log handling code we have in bitbake, we should just mirror > the console output to a logfile somewhere in TMPDIR automatically... That sounds like a good approach to me as well.
Fixed in master in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5f8b0ef64eea962b14da295f993c2cc436c37bea and http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2d8e5349a3dec405e005dc249d1412bad5a5977b