Bug 8856 - autoconf errors pasting output of config.log isn't always helpful
Summary: autoconf errors pasting output of config.log isn't always helpful
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.1 M3
Assignee: Ross Burton
QA Contact: Costin
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-12-22 22:01 UTC by Paul Eggleton
Modified: 2016-02-05 13:24 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.