mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: 2.5.50 / compiling with frame pointers doesn't
Date: Sat, 30 Nov 2002 11:44:13 +1100	[thread overview]
Message-ID: <20021130004413.GB3831@zip.com.au> (raw)

As near as I can tell, compiling with frame pointers turned on doesn't
do anything. I had a quick look around in the Makefiles and found that
the test for CONFIG_FRAME_POINTER happens -before- the .config is
actually loaded, thereby resulting in it never being defined and so
-fomit-frame-pointer is always included.

Now I'm not too sure as the whole Makefile structure in the linux kernel
but the way I fixed this was by moving the test block down to be below
.config getting loaded rather then moving the .config load section up.
Not sure which is preferrable but here's my patch.

--- Makefile.old	Sat Nov 30 11:43:08 2002
+++ Makefile	Thu Nov 28 22:56:02 2002
@@ -169,9 +169,6 @@
 CPPFLAGS	:= -D__KERNEL__ -Iinclude
 CFLAGS 		:= $(CPPFLAGS) -Wall -Wstrict-prototypes -Wno-trigraphs -O2 \
 	  	   -fno-strict-aliasing -fno-common
-ifndef CONFIG_FRAME_POINTER
-CFLAGS		+= -fomit-frame-pointer
-endif
 AFLAGS		:= -D__ASSEMBLY__ $(CPPFLAGS)
 
 export	VERSION PATCHLEVEL SUBLEVEL EXTRAVERSION KERNELRELEASE ARCH \
@@ -221,6 +218,10 @@
 
 -include .config
 
+endif
+
+ifndef CONFIG_FRAME_POINTER
+CFLAGS		+= -fomit-frame-pointer
 endif
 
 include arch/$(ARCH)/Makefile

-- 
        All people are equal,
        But some are more equal then others.
            - George W. Bush Jr, President of the United States
              September 21, 2002 (Abridged version of security speech)

                 reply	other threads:[~2002-11-30  0:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021130004413.GB3831@zip.com.au \
    --to=cat@zip.com.au \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome