mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: viro@ZenIV.linux.org.uk, sam@ravnborg.org, zippel@linux-m68k.org
Cc: linux-kernel@vger.kernel.org
Subject: Immortal CONFIG_DEBUG_INFO=y
Date: Sun, 16 Nov 2008 10:42:01 +0300	[thread overview]
Message-ID: <20081116074201.GA27921@x200.localdomain> (raw)

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.

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16  7:42 Alexey Dobriyan [this message]
2008-11-16  7:49 ` Sam Ravnborg
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=20081116074201.GA27921@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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®