Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: "Kip Walker" <kwalker@broadcom.com>
Cc: linux-mips@linux-mips.org, "Ralf Baechle" <ralf@linux-mips.org>
Subject: Re: [PATCH] add CONFIG_DEBUG_INFO
Date: Mon, 03 Mar 2003 20:50:28 +0100	[thread overview]
Message-ID: <86d6l8fcvv.fsf@trasno.mitica> (raw)
In-Reply-To: <3E63B047.D3BA2A2C@broadcom.com> ("Kip Walker"'s message of "Mon, 03 Mar 2003 11:43:03 -0800")

>>>>> "kip" == Kip Walker <kwalker@broadcom.com> writes:

Hi

kip> KipIndex: arch/mips/config-shared.in
kip> ===================================================================
kip> RCS file: /home/cvs/linux/arch/mips/Attic/config-shared.in,v
kip> retrieving revision 1.1.2.48
kip> diff -u -r1.1.2.48 config-shared.in
kip> --- arch/mips/config-shared.in	26 Feb 2003 21:14:23 -0000	1.1.2.48
kip> +++ arch/mips/config-shared.in	3 Mar 2003 19:41:11 -0000
kip> @@ -976,6 +976,7 @@
 
kip> bool 'Are you using a crosscompiler' CONFIG_CROSSCOMPILE
kip> bool 'Enable run-time debugging' CONFIG_RUNTIME_DEBUG
kip> +bool 'Debugging symbols' CONFIG_DEBUG_INFO
kip> bool 'Remote GDB kernel debugging' CONFIG_KGDB
kip> dep_bool '  Console output to GDB' CONFIG_GDB_CONSOLE $CONFIG_KGDB
kip> if [ "$CONFIG_SIBYTE_SB1xxx_SOC" = "y" ]; then

Once there, doing something like:

bool 'Remote GDB kernel debugging' CONFIG_KGDB
if [ "$CONFIG_KGDB" = "y" ]; then
   define_bool CONFIG_DEBUG_INFO n
else
   bool 'Debugging symbols' CONFIG_DEBUG_INFO
fi

And you can use single ifdefs in Makefiles?

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  parent reply	other threads:[~2003-03-03 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 19:34 [PATCH] rename CONFIG_REMOTE_DEBUG and CONFIG_DEBUG Jun Sun
2003-03-03 19:43 ` [PATCH] add CONFIG_DEBUG_INFO Kip Walker
2003-03-03 19:45   ` Kip Walker
2003-03-03 19:50   ` Juan Quintela [this message]
2003-03-06 16:47     ` Kip Walker
2003-03-07 13:48       ` Juan Quintela
2003-03-07 15:21         ` Ralf Baechle
2003-03-07 15:27         ` Kip Walker

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=86d6l8fcvv.fsf@trasno.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=kwalker@broadcom.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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