]> code.ossystems Code Review - openembedded-core.git/commit
Use die() or bbfatal_log() where the log should definitely be printed
authorPaul Eggleton <paul.eggleton@linux.intel.com>
Mon, 13 Jul 2015 15:20:03 +0000 (16:20 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 16 Jul 2015 14:08:45 +0000 (15:08 +0100)
commit04ed9a19e1b08003329138b8ab83691d13c11fd9
tree94eb3c9809969af693a37725bb13f8f9e4c8e4c4
parentbeec1cf3d22d7dbe85f332a055c72649f4bd3e92
Use die() or bbfatal_log() where the log should definitely be printed

Change calls to bbfatal() to either die() or bbfatal_log() where we know
we want the full log to be printed by the UI (calling bberror or bbfatal
would otherwise suppress it since the change to connect these functions
through to the UI.) bbfatal() is still fine to use where there is enough
context information in the message such that the log isn't needed.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
meta/classes/autotools.bbclass
meta/classes/kernel-yocto.bbclass
meta/classes/scons.bbclass
meta/recipes-extended/groff/groff_1.22.3.bb