From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: [COMMIT] Fix file-name clashes in gdbserver/
Date: Sun, 29 May 2005 14:11:00 -0000 [thread overview]
Message-ID: <uy89y8oo8.fsf@gnu.org> (raw)
This change:
2005-05-28 Daniel Jacobowitz <dan@codesourcery.com>
* Makefile.in (SFILES): Add linux-ppc64-low.c.
(linux-ppc64-low.o, reg-ppc64.c, reg-ppc64.o): New targets.
* configure.srv: Add powerpc64-*-linux*.
* linux-ppc64-low.c: New file.
required a tweak for fnchange.lst, to resolve clashes between the new
linux-ppc64-low.c and the existing linux-ppc-low.c. I committed the
following patch as an obvious fix:
2005-05-29 Eli Zaretskii <eliz@gnu.org>
* config/djgpp/fnchange.lst: Add mappings for linux-ppc-low.c and
linux-ppc64-low.c.
Index: gdb/config/djgpp/fnchange.lst
===================================================================
RCS file: /cvs/src/src/gdb/config/djgpp/fnchange.lst,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -r1.91 -r1.92
--- gdb/config/djgpp/fnchange.lst 24 May 2005 08:27:01 -0000 1.91
+++ gdb/config/djgpp/fnchange.lst 29 May 2005 07:36:09 -0000 1.92
@@ -110,6 +110,8 @@
@V@/gdb/f-exp.tab.c @V@/gdb/f-exp_tab.c
@V@/gdb/gdbserver/linux-cris-low.c @V@/gdb/gdbserver/lx-cris.c
@V@/gdb/gdbserver/linux-crisv32-low.c @V@/gdb/gdbserver/lx-cris32.c
+@V@/gdb/gdbserver/linux-ppc-low.c @V@/gdb/gdbserver/lx-ppc-low.c
+@V@/gdb/gdbserver/linux-ppc64-low.c @V@/gdb/gdbserver/lx-ppc64-low.c
@V@/gdb/gdbtk/ChangeLog-2001 @V@/gdb/gdbtk/ChangeLog.001
@V@/gdb/gdbtk/ChangeLog-2002 @V@/gdb/gdbtk/ChangeLog.002
@V@/gdb/gdbtk/ChangeLog-2003 @V@/gdb/gdbtk/ChangeLog.003
next reply other threads:[~2005-05-29 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 14:11 Eli Zaretskii [this message]
2005-05-29 14:26 ` Daniel Jacobowitz
2005-05-29 18:19 ` Eli Zaretskii
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=uy89y8oo8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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