All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] 2.6 kbuild inconsistent CONFIG_DEBUG_INFO usage?
Date: Thu, 28 Jul 2005 21:41:22 +0000	[thread overview]
Message-ID: <20050728214122.GF2249@homer.coderock.org> (raw)
In-Reply-To: <hdage1thbneer1ucku4amfkjsq5tnlf50m@4ax.com>

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

On 29/07/05 07:14 +1000, Grant Coady wrote:
> On Thu, 28 Jul 2005 22:21:49 +0200, Domen Puncer <domen@coderock.org> wrote:
> >> 
> >> Most users test if the flag is set, some users test == 'y', nothing 
> >> checks for == 'n'.  So if I "Set CONFIG_DEBUG_INFO=n" I get unwanted 
> >> debugging info, opposite result to what was intended?
> >
> >CONFIG_DEBUG_INFO == y compiles debugging info in kernel, and is
> >useful for kernel debuggers (and probably more).
> >For compile tests this option doesn't really mater, as it is not
> >compile time debugging. But disabling it makes compiles faster,
> >which is good.
> 
> top-level 2.6.12.3 Makefile:
> ...
> ifdef CONFIG_DEBUG_INFO
> CFLAGS          += -g
> endif
> ...
> 
> So please tell me how "CONFIG_DEBUG_INFO=n" disables debug?

Ugh, I see the point, I should have read more carefully.
But Nishanth is right, kconfig magic makes this work :-)

domen@homer:~/kernel/a$ grep CONFIG_DEBUG_INFO build/.config
CONFIG_DEBUG_INFO=n
domen@homer:~/kernel/a$ make O=`pwd`/build/ oldconfig >/dev/null
domen@homer:~/kernel/a$ grep CONFIG_DEBUG_INFO build/.config
# CONFIG_DEBUG_INFO is not set

And yes, "just make" will take care of it too.


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2005-07-28 21:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28  0:41 [KJ] 2.6 kbuild inconsistent CONFIG_DEBUG_INFO usage? Grant Coady
2005-07-28  4:43 ` Nishanth Aravamudan
2005-07-28 19:40 ` Grant Coady
2005-07-28 20:21 ` Domen Puncer
2005-07-28 20:38 ` Nishanth Aravamudan
2005-07-28 21:14 ` Grant Coady
2005-07-28 21:17 ` Grant Coady
2005-07-28 21:41 ` Domen Puncer [this message]

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=20050728214122.GF2249@homer.coderock.org \
    --to=domen@coderock.org \
    --cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.