mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: viro@ZenIV.linux.org.uk, zippel@linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: Immortal CONFIG_DEBUG_INFO=y
Date: Sun, 16 Nov 2008 08:49:48 +0100	[thread overview]
Message-ID: <20081116074948.GA32670@uranus.ravnborg.org> (raw)
In-Reply-To: <20081116074201.GA27921@x200.localdomain>

On Sun, Nov 16, 2008 at 10:42:01AM +0300, Alexey Dobriyan wrote:
> 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.

Because that defconfig does:
CONFIG_SH_KGDB=y

and SH_KGDB does:
	select DEBUG_INFO

Instead of editing the Kconfig file you should use the KCONFIG_ALLCONFIG trick.
See README for usage.

	Sam

  reply	other threads:[~2008-11-16  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16  7:42 Alexey Dobriyan
2008-11-16  7:49 ` Sam Ravnborg [this message]
2008-11-16  8:03   ` Alexey Dobriyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081116074948.GA32670@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®