6943 2014-11-07 21:36:18 +0000 kernel-dev: make Kconfig audit output visible 2017-06-07 19:43:15 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 1.8 x86 Multiple RESOLVED FIXED Medium+ enhancement 1.8 M4 1 bruce.ashfield bruce.ashfield alexandru.c.georgescu bluelightning bruce.ashfield dvhart jose.perez.carranza philip tom.zanussi davidx.lopez.barriba --- --- Don't know oldest_to_newest 46878 0 bruce.ashfield 2014-11-07 21:36:18 +0000 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. 47162 1 dvhart 2014-11-24 16:08:05 +0000 Bruce, marking as M1 as I believe this is part of your pending patchset. Please update accordingly if not. 47239 2 bruce.ashfield 2014-11-27 16:09:29 +0000 Nearly done. but rather than cram everything in late in M1, bumping to M2 where I'll submit in smaller batches. 47764 3 philip 2015-01-07 14:31:56 +0000 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! 48975 4 bruce.ashfield 2015-02-22 14:12:11 +0000 This has been merged to oe-core.