From: "Kip Walker" <kwalker@broadcom.com>
To: linux-mips@linux-mips.org
Cc: "Ralf Baechle" <ralf@linux-mips.org>
Subject: Re: [PATCH] add CONFIG_DEBUG_INFO
Date: Thu, 06 Mar 2003 08:47:16 -0800 [thread overview]
Message-ID: <3E677B94.AE22C65D@broadcom.com> (raw)
In-Reply-To: 86d6l8fcvv.fsf@trasno.mitica
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
Any more comments on this topic? Here's a patch that incorporates
Juan's suggestion. I'm content to do away with the multiple-dependence
syntax in the Makefiles... having KGDB on defines "CONFIG_DEBUG_INFO",
otherwise you can explicitly turn it on. If no one objects, I'll do the
same for 2.5.
Kip
[-- Attachment #2: debug.diff --]
[-- Type: text/plain, Size: 2206 bytes --]
Index: arch/mips/config-shared.in
===================================================================
RCS file: /home/cvs/linux/arch/mips/Attic/config-shared.in,v
retrieving revision 1.1.2.48
diff -u -r1.1.2.48 config-shared.in
--- arch/mips/config-shared.in 26 Feb 2003 21:14:23 -0000 1.1.2.48
+++ arch/mips/config-shared.in 6 Mar 2003 16:43:59 -0000
@@ -977,6 +977,11 @@
bool 'Are you using a crosscompiler' CONFIG_CROSSCOMPILE
bool 'Enable run-time debugging' CONFIG_RUNTIME_DEBUG
bool 'Remote GDB kernel debugging' CONFIG_KGDB
+if [ "$CONFIG_KGDB" = "y" ]; then
+ define_bool CONFIG_DEBUG_INFO y
+else
+ bool 'Debugging symbols' CONFIG_DEBUG_INFO
+fi
dep_bool ' Console output to GDB' CONFIG_GDB_CONSOLE $CONFIG_KGDB
if [ "$CONFIG_SIBYTE_SB1xxx_SOC" = "y" ]; then
bool 'Compile for Corelis Debugger' CONFIG_SB1XXX_CORELIS
Index: arch/mips/Makefile
===================================================================
RCS file: /home/cvs/linux/arch/mips/Makefile,v
retrieving revision 1.78.2.23
diff -u -r1.78.2.23 Makefile
--- arch/mips/Makefile 26 Feb 2003 21:14:23 -0000 1.78.2.23
+++ arch/mips/Makefile 6 Mar 2003 16:43:59 -0000
@@ -41,11 +41,11 @@
LINKFLAGS += -G 0 -static # -N
MODFLAGS += -mlong-calls
-ifdef CONFIG_KGDB
+ifdef CONFIG_DEBUG_INFO
GCCFLAGS += -g
+endif
ifdef CONFIG_SB1XXX_CORELIS
GCCFLAGS += -mno-sched-prolog -fno-omit-frame-pointer
-endif
endif
check_gcc = $(shell if $(CC) $(1) -S -o /dev/null -xc /dev/null > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
Index: arch/mips64/Makefile
===================================================================
RCS file: /home/cvs/linux/arch/mips64/Makefile,v
retrieving revision 1.22.2.27
diff -u -r1.22.2.27 Makefile
--- arch/mips64/Makefile 26 Feb 2003 21:14:24 -0000 1.22.2.27
+++ arch/mips64/Makefile 6 Mar 2003 16:43:59 -0000
@@ -39,11 +39,11 @@
LINKFLAGS += -G 0 -static # -N
MODFLAGS += -mlong-calls
-ifdef CONFIG_KGDB
+ifdef CONFIG_DEBUG_INFO
GCCFLAGS += -g
+endif
ifdef CONFIG_SB1XXX_CORELIS
GCCFLAGS += -mno-sched-prolog -fno-omit-frame-pointer
-endif
endif
check_gcc = $(shell if $(CC) $(1) -S -o /dev/null -xc /dev/null > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi)
next prev parent reply other threads:[~2003-03-06 16:47 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
2003-03-06 16:47 ` Kip Walker [this message]
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=3E677B94.AE22C65D@broadcom.com \
--to=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 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.