From beec1cf3d22d7dbe85f332a055c72649f4bd3e92 Mon Sep 17 00:00:00 2001 From: Paul Eggleton Date: Mon, 13 Jul 2015 16:30:09 +0100 Subject: classes/base: fix die() to print the full log The recent change to connect through the shell logging functions caused a regression - bb.error() and bb.fatal() cause a flag to be set internally such that BitBake's UI will not print the full task log on failure; unfortunately we have in a lot of places called die() or bbfatal() within shell functions with a very terse message as a means of exiting out, where we still want to see the full log (and we were previously). We do still want to have fatal errors with proper messages that don't result in the full log being printed, however we can't ignore the typical usage of die(). Having added a mechanism to BitBake to log an error and reset the flag, create a bbfatal_log() function that uses this and call it from die() to restore the previous behaviour. Signed-off-by: Paul Eggleton --- meta/classes/logging.bbclass | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'meta/classes/logging.bbclass') diff --git a/meta/classes/logging.bbclass b/meta/classes/logging.bbclass index f19edddde5..6b24839af5 100644 --- a/meta/classes/logging.bbclass +++ b/meta/classes/logging.bbclass @@ -40,6 +40,14 @@ bbfatal() { exit 1 } +# Like bbfatal, except prevents the suppression of the error log by +# bitbake's UI. +# Output: logs console +bbfatal_log() { + printf "%b\0" "bbfatal_log $*" > ${LOGFIFO} + exit 1 +} + # Print debug messages. These are appropriate for progress checkpoint # messages to the logs. Depending on the debug log level, they may also # go to the console. -- cgit 1.2.3-korg