From: Adrian Bunk <bunk@stusta.de>
To: spyro@f2s.com
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] arm26: one -g is enough for everyone ;-)
Date: Wed, 10 Aug 2005 02:24:01 +0200 [thread overview]
Message-ID: <20050810002401.GO4006@stusta.de> (raw)
The main Makefile is already adding -g to the CFLAGS if
CONFIG_DEBUG_INFO=y.
Not that two -g would do harm, but one works as well.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.13-rc5-mm1/arch/arm26/Makefile.old 2005-08-10 02:18:56.000000000 +0200
+++ linux-2.6.13-rc5-mm1/arch/arm26/Makefile 2005-08-10 02:19:28.000000000 +0200
@@ -17,10 +17,6 @@
CFLAGS +=-fno-omit-frame-pointer -mno-sched-prolog
endif
-ifeq ($(CONFIG_DEBUG_INFO),y)
-CFLAGS +=-g
-endif
-
CFLAGS_BOOT :=-mapcs-26 -mcpu=arm3 -msoft-float -Uarm
CFLAGS +=-mapcs-26 -mcpu=arm3 -msoft-float -Uarm
AFLAGS +=-mapcs-26 -mcpu=arm3 -msoft-float
next reply other threads:[~2005-08-10 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 0:24 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 20:28 [2.6 patch] arm26: one -g is enough for everyone ;-) Adrian Bunk
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=20050810002401.GO4006@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=spyro@f2s.com \
/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