From: Elena Zannoni <ezannoni@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] add linux-nat.o to ppc64 builds
Date: Fri, 27 Jun 2003 17:02:00 -0000 [thread overview]
Message-ID: <16124.31321.401483.631867@localhost.redhat.com> (raw)
I think this qualifies as obvious. Fixes a build problem on ppc64
hosts. I am checking this in the branch and mainline.
elena
2003-06-27 Elena Zannoni <ezannoni@redhat.com>
* config/powerpc/ppc64-linux.mh (NATDEPFILES): Add linux-nat.o.
Index: ppc64-linux.mh
===================================================================
RCS file: /cvs/uberbaum/gdb/config/powerpc/ppc64-linux.mh,v
retrieving revision 1.2
diff -u -p -r1.2 ppc64-linux.mh
--- ppc64-linux.mh 12 Jun 2003 23:30:39 -0000 1.2
+++ ppc64-linux.mh 27 Jun 2003 17:01:05 -0000
@@ -6,7 +6,7 @@ XM_CLIBS=
NAT_FILE= nm-ppc64-linux.h
NATDEPFILES= infptrace.o inftarg.o fork-child.o linux-proc.o \
ppc-linux-nat.o proc-service.o thread-db.o lin-lwp.o \
- gcore.o
+ gcore.o linux-nat.o
# The PowerPC has severe limitations on TOC size, and uses them even
# for non-PIC code. GDB overflows those tables when compiling with
next reply other threads:[~2003-06-27 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 17:02 Elena Zannoni [this message]
2003-06-27 17:07 ` 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=16124.31321.401483.631867@localhost.redhat.com \
--to=ezannoni@redhat.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