lkml.org 
[lkml]   [2008]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectImmortal CONFIG_DEBUG_INFO=y
As known to everybody doing fat builds, banning DEBUG_INFO=y is mandatory,
otherwise build is slower and takes much more disk space. And to not
accidently enable it, banning it in kconfig:

@@ -475,7 +475,7 @@ config DEBUG_BUGVERBOSE

config DEBUG_INFO
bool "Compile the kernel with debug info"
- depends on DEBUG_KERNEL
+ depends on DEBUG_KERNEL && DISABLED
help
If you say Y here the resulting kernel image will include
debugging info resulting in a larger kernel image.

This works pretty well -- allmodconfig generates config without DEBUG_INFO and
so on, defconfigs also regenerated without it, even if original one in arch/
has DEBUG_INFO enabled and so on. Trick also works for other options, like,
KALLSYMS_EXTRA_PASS.

Except one case:

make ARCH=sh magicpanelr2_defconfig

DEBUG_INFO survives to .config and resulting build runs with -g.

Now, DEBUG_INFO correctly dissapeares for all other defconfig.
And it dissapeares in se7721_defconfig case (which has CONFIG_DEBUG_KERNEL=y
_and_ CONFIG_DEBUG_INFO=y)

All other options I ban and enable (LOCALVERSION_AUTO, KALLSYMS_EXTRA_PASS,
MODVERSIONS, MODULE_SRCVERSION_ALL, STANDALONE, STAGING) correctly on and off
themselves in all cases.


\
 
 \ /
  Last update: 2008-11-16 08:41    [W:0.031 / U:1.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site