summaryrefslogtreecommitdiffstats
path: root/meta/classes/autotools.bbclass
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2015-07-13 16:30:09 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-07-16 15:09:23 +0100
commit757be608a5538bc4f32d234f216d24d4caa6539b (patch)
tree91ae049b5e261af35587f124b81ba112b3d3a5c2 /meta/classes/autotools.bbclass
parent546bfe8069cfaffd970ba4f6d7fc29fa8070f319 (diff)
downloadpoky-757be608a5538bc4f32d234f216d24d4caa6539b.tar.gz
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. (From OE-Core rev: beec1cf3d22d7dbe85f332a055c72649f4bd3e92) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/autotools.bbclass')
0 files changed, 0 insertions, 0 deletions