Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] use CFLAGS when compiling (PPC64)
Date: Wed, 07 Apr 2004 20:11:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0404071458500.9321@lazy> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 166 bytes --]


This patch add CFLAGS to the compile line for building gdbserver,
gdbreplay and tclsh. Compiling GDB as 64bit binary on PPC64 breaks without
this.

Thanks
Manoj Iyer

[-- Attachment #2: add CFLAGS patch --]
[-- Type: TEXT/PLAIN, Size: 1278 bytes --]

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

             reply	other threads:[~2004-04-07 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 20:11 Manoj Iyer [this message]
2004-04-29 16:03 ` Andrew Cagney
2004-04-29 21:12   ` Daniel Jacobowitz

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.58.0404071458500.9321@lazy \
    --to=manjo@austin.ibm.com \
    --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