Bug 6943

Summary: kernel-dev: make Kconfig audit output visible
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Bruce Ashfield <bruce.ashfield>
Component: kernelAssignee: Bruce Ashfield <bruce.ashfield>
Status: RESOLVED FIXED QA Contact: David Lopez Barriba <davidx.lopez.barriba>
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, bluelightning, bruce.ashfield, dvhart, jose.perez.carranza, philip, tom.zanussi
Version: 1.8   
Target Milestone: 1.8 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Bruce Ashfield 2014-11-07 21:36:18 UTC 
The output of the Kconfig audit was previously visible, and then hidden. But since it is
no longer visible, it is not augmenting the kernel development process.

This information needs to be made visible, but not alarm the user, or break the build when
warnings are generated.
Comment 1 Darren Hart 2014-11-24 16:08:05 UTC 
Bruce, marking as M1 as I believe this is part of your pending patchset. Please update accordingly if not.
Comment 2 Bruce Ashfield 2014-11-27 16:09:29 UTC 
Nearly done. but rather than cram everything in late in M1, bumping to M2 where I'll submit in smaller batches.
Comment 3 Phlip Balister 2015-01-07 14:31:56 UTC 
The lack of output is making it extremely difficult to debug issues as you work with kernel recipes. If I add an option via a .cfg file, there is no sign that is did not make it into the final .config file.

This just cost me about six hours fixing a stupid option dependency issue in a cfg file because I couldn't be sure what was really going on during the kernel build process.

Quite frankly, if something in a cfg file doesn't get into the final kernel config, YOU NEED TO ALARM THE USER AND BREAK THE BUILD!
Comment 4 Bruce Ashfield 2015-02-22 14:12:11 UTC 
This has been merged to oe-core.