Bug 8856

Summary: autoconf errors pasting output of config.log isn't always helpful
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: coreAssignee: Ross Burton <ross.burton>
Status: VERIFIED FIXED QA Contact: Costin <costin.c.constantin>
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, meta.mr.watcher, meta.watcher
Version: 2.0   
Target Milestone: 2.1 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Paul Eggleton 2015-12-22 22:01:49 UTC 
When I'm building a new recipe locally, If I get an error during configure then the entire config.log gets printed in the output "to aid debugging". Often however if a check fails, it's reasonably obvious as to what needs doing - so the massive spew of config.log only gets in the way.

I think we ought to re-evaluate whether this always needs to be shown - can we detect if it's necessary? If not can we have it controlled by a variable, off by default and perhaps enabled for the autobuilder if that's where we need it?
Comment 1 Ross Burton 2015-12-22 22:16:46 UTC 
Agreed, and I think an option is just the right thing.  Either print the full log, or show where the full log is.
Comment 2 Ross Burton 2016-01-26 14:22:21 UTC 
Merged in oe-core 55e263c559098cce99d8c3ef57ccc39f1d4a6848.
Comment 3 Costin 2016-02-05 13:24:50 UTC 
Hello,

Checked on latest master on http://errors.yoctoproject.org/Errors/Latest/Autobuilder/ and config.log content is not present.

Marking as verified.