diff options
| author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2015-07-13 16:30:09 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-07-16 15:08:45 +0100 |
| commit | beec1cf3d22d7dbe85f332a055c72649f4bd3e92 (patch) | |
| tree | 5e08956d90b46416b32e38203fca1db057cb39d6 /meta/classes/kernel-yocto.bbclass | |
| parent | dd7449114a33c92a2877b1a6f875d812b10856ff (diff) | |
| download | openembedded-core-beec1cf3d22d7dbe85f332a055c72649f4bd3e92.tar.gz openembedded-core-beec1cf3d22d7dbe85f332a055c72649f4bd3e92.tar.bz2 openembedded-core-beec1cf3d22d7dbe85f332a055c72649f4bd3e92.zip | |
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 <paul.eggleton@linux.intel.com>
Diffstat (limited to 'meta/classes/kernel-yocto.bbclass')
0 files changed, 0 insertions, 0 deletions