[OE-core] [PATCH] autotools.bbclass: output failed config.log
Hongxu Jia
hongxu.jia at windriver.com
Wed May 15 09:50:44 UTC 2019
On 5/15/19 5:32 PM, Andreas Müller wrote:
>> --- a/meta/classes/autotools.bbclass
>> +++ b/meta/classes/autotools.bbclass
>> @@ -90,7 +90,11 @@ oe_runconf () {
>> bbnote "Running $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} $@"
>> if ! ${CACHED_CONFIGUREVARS} $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} "$@"; then
>> bbnote "The following config.log files may provide further information."
>> - bbnote `find ${B} -ignore_readdir_race -type f -name config.log`
>> + config_log="`find ${B} -ignore_readdir_race -type f -name config.log`"
>> + bbnote "$config_log"
>> + [ -e "$config_log" ] && cat "$config_log" | while read line; do
>> + bbnote "$line"
>> + done
>> bbfatal_log "configure failed"
>> fi
>> else
>> --
>> 2.7.4
>>
> That output is useful only sometimes and extremly verbose. I'd suggest
> to introduce a switch to enable/disable (even as newbie user I am able
> to find config.log). How about making autobuilder's WORKDIR
> accessible?
The output only happens while do_configure failure, it does nothing when
build succeed,
while failure occurs, I believe related message is the more the better.
The autobuilder is just an example, for community development, it is
hard to login
others build host to debug issue, and we have to take time to reproduce it
if we could trace it with a simple glance from the log, why not
//Hongxu
> Andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20190515/a796f7c4/attachment.html>
More information about the Openembedded-core
mailing list