From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Manoj Iyer <manjo@austin.ibm.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] use CFLAGS when compiling (PPC64)
Date: Thu, 29 Apr 2004 21:12:00 -0000 [thread overview]
Message-ID: <20040429211236.GA27523@nevyn.them.org> (raw)
In-Reply-To: <40912759.1080706@gnu.org>
On Thu, Apr 29, 2004 at 12:03:37PM -0400, Andrew Cagney wrote:
> >This patch add CFLAGS to the compile line for building gdbserver,
> >gdbreplay and tclsh. Compiling GDB as 64bit binary on PPC64 breaks without
> >this.
>
> Daniel, did this get rejected? I recall it being pointed out that the
> correct way to build such a beastie was with:
>
> CC='gcc -m64' ./configure && gmake
>
> and I know that already works.
It wasn't rejected but I think it should be. It seems reasonable, but
if something needs to be added to link command lines, it should be in
$CC or in $LDFLAGS. I don't know what the GNU coding standards have to
say about that, though - just my opinion.
> >diff -Naurd old/src/gdb/gdbserver/Makefile.in
> >new/src/gdb/gdbserver/Makefile.in
> >--- old/src/gdb/gdbserver/Makefile.in 2004-03-04 16:59:10.000000000 -0500
> >+++ new/src/gdb/gdbserver/Makefile.in 2004-04-07 15:04:06.398979032 -0500
> >@@ -171,12 +171,12 @@
> >
> > gdbserver: $(OBS) ${ADD_DEPS} ${CDEPS}
> > rm -f gdbserver
> >- ${CC-LD} $(GLOBAL_CFLAGS) $(LDFLAGS) -o gdbserver $(OBS) \
> >+ ${CC-LD} $(GLOBAL_CFLAGS) $(CFLAGS) $(LDFLAGS) -o gdbserver $(OBS) \
> > $(GDBSERVER_LIBS) $(XM_CLIBS)
> >
> > gdbreplay: gdbreplay.o
> > rm -f gdbreplay
> >- ${CC-LD} $(GLOBAL_CFLAGS) $(LDFLAGS) -o gdbreplay gdbreplay.o \
> >+ ${CC-LD} $(GLOBAL_CFLAGS) $(CFLAGS) $(LDFLAGS) -o gdbreplay
> >gdbreplay.o \
> > $(XM_CLIBS)
> >
> > # Put the proper machine-specific files first, so M-. on a machine
> >diff -Naurd old/src/tcl/unix/Makefile.in new/src/tcl/unix/Makefile.in
> >--- old/src/tcl/unix/Makefile.in 2003-01-21 14:40:18.000000000 -0500
> >+++ new/src/tcl/unix/Makefile.in 2004-04-07 15:05:09.046041896 -0500
> >@@ -477,7 +477,7 @@
> >
> >
> > tclsh: ${TCLSH_OBJS} ${TCL_LIB_FILE}
> >- ${CC} ${LDFLAGS} ${TCLSH_OBJS} @TCL_BUILD_LIB_SPEC@ ${LIBS} \
> >+ ${CC} ${CFLAGS} ${LDFLAGS} ${TCLSH_OBJS} @TCL_BUILD_LIB_SPEC@
> >${LIBS} \
> > ${CC_SEARCH_FLAGS} -o tclsh
> >
> > # Resetting the LIB_RUNTIME_DIR below is required so that
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-04-29 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 20:11 Manoj Iyer
2004-04-29 16:03 ` Andrew Cagney
2004-04-29 21:12 ` Daniel Jacobowitz [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=20040429211236.GA27523@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=manjo@austin.ibm.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