From: Peter Breitenlohner <peb@mppmu.mpg.de>
To: gdb-patches@sources.redhat.com
Subject: Re: gdb-5.3 -- some minor build problems + 3 patches
Date: Wed, 22 Jan 2003 18:30:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.50.0301221927360.4506-200000@pcl321.mppmu.mpg.de> (raw)
In-Reply-To: <Pine.LNX.4.50.0301221920290.4506-200000@pcl321.mppmu.mpg.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 454 bytes --]
and here the second patch:
LDFLAGS were not propagated from gdb to gdb/gdbserver.
Consequently "make LDFLAGS=-s" did produced unstripped gdbreplay and
gdbserver binaries.
All this wouldn't be needed, if the gdb distribution were to support
"make install-strip" as most modern packages do. Unfortunately this
feature has not (yet?) found its way into the cygnus type source
trees (nor has DESTDIR support).
Peter Breitenlohner <peb@mppmu.mpg.de>
[-- Attachment #2: Type: TEXT/PLAIN, Size: 906 bytes --]
LDFLAGS were not propagated from gdb to gdb/gdbserver.
Consequently "make LDFLAGS=-s" did produced unstripped gdbreplay and
gdbserver binaries.
All this wouldn't be needed, if the gdb distribution were to support
"make install-strip" as most modern packages do. Unfortunately this
feature has not (yet?) found its way into the cygnus type source
trees (nor has DESTDIR support).
diff -ur gdb+dejagnu-weekly-CVS-20030121.orig/src/gdb/Makefile.in gdb+dejagnu-weekly-CVS-20030121/src/gdb/Makefile.in
--- gdb+dejagnu-weekly-CVS-20030121.orig/src/gdb/Makefile.in 2003-01-18 18:25:22.000000000 +0100
+++ gdb+dejagnu-weekly-CVS-20030121/src/gdb/Makefile.in 2003-01-22 19:04:56.000000000 +0100
@@ -431,6 +431,7 @@
"CXX=$(CXX)" \
"CXXFLAGS=$(CXXFLAGS)" \
"DLLTOOL=$(DLLTOOL)" \
+ "LDFLAGS=$(LDFLAGS)" \
"RANLIB=$(RANLIB)" \
"MAKEINFO=$(MAKEINFO)" \
"MAKEHTML=$(MAKEHTML)" \
prev parent reply other threads:[~2003-01-22 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301221743.h0MHhUc29957@duracef.shout.net>
2003-01-22 18:26 ` Peter Breitenlohner
2003-01-22 18:30 ` Peter Breitenlohner [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=Pine.LNX.4.50.0301221927360.4506-200000@pcl321.mppmu.mpg.de \
--to=peb@mppmu.mpg.de \
--cc=gdb-patches@sources.redhat.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