From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: [rfa] DJGPP updates
Date: Sun, 22 Jan 2006 16:28:00 -0000 [thread overview]
Message-ID: <20060122162756.GA24068@nevyn.them.org> (raw)
Do these look OK, Eli?
I tried to test the to_create_inferior patch on DJGPP; however, the current
GCC 4.0.1 packages can not run GDB's configure script (internal error
shortly after testing for <gmp.h>). But at least I got this done.
--
Daniel Jacobowitz
CodeSourcery
2006-01-22 Daniel Jacobowitz <dan@codesourcery.com>
* config/djgpp/README: Typo fix.
* config/djgpp/fnchange.lst: Update.
Index: gdb/config/djgpp/README
===================================================================
RCS file: /cvs/src/src/gdb/config/djgpp/README,v
retrieving revision 1.8
diff -u -p -r1.8 README
--- gdb/config/djgpp/README 11 May 2005 07:29:35 -0000 1.8
+++ gdb/config/djgpp/README 22 Jan 2006 16:24:12 -0000
@@ -160,7 +160,7 @@ The test suite has been made to work wit
in some of the programs, or want to be sure you have a fully
functional GDB executable, it is a good idea to run the test suite.
You cannot use "make check" for that, since it will want to run the
-`dejagnu' utility which GDB doesn't support. Instead, use the special
+`dejagnu' utility which DJGPP doesn't support. Instead, use the special
script gdb/config/djgpp/djcheck.sh, like this:
cd gdb/testsuite
Index: gdb/config/djgpp/fnchange.lst
===================================================================
RCS file: /big/fsf/rsync/src/src/gdb/config/djgpp/fnchange.lst,v
retrieving revision 1.93
diff -u -p -r1.93 fnchange.lst
--- gdb/config/djgpp/fnchange.lst 10 Sep 2005 18:11:09 -0000 1.93
+++ gdb/config/djgpp/fnchange.lst 22 Jan 2006 16:23:53 -0000
@@ -5,6 +5,8 @@
@V@/bfd/ChangeLog-9899 @V@/bfd/ChangeLog.9899
@V@/bfd/ChangeLog-0001 @V@/bfd/ChangeLog.0001
@V@/bfd/ChangeLog-0203 @V@/bfd/ChangeLog.0203
+@V@/bfd/ChangeLog-2004 @V@/bfd/ChangeLog.004
+@V@/bfd/ChangeLog-2005 @V@/bfd/ChangeLog.005
@V@/bfd/doc/ChangeLog-9103 @V@/bfd/ChangeLog.9103
@V@/bfd/coff-tic30.c @V@/bfd/cofftic30.c
@V@/bfd/coff-tic4x.c @V@/bfd/cofftic40.c
@@ -23,6 +25,8 @@
@V@/bfd/elf32-frv.c @V@/bfd/elf32fv.c
@V@/bfd/elf32-i370.c @V@/bfd/e32i370.c
@V@/bfd/elf32-i386.c @V@/bfd/e32i86.c
+@V@/bfd/elf32-m32c.c @V@/bfd/em32c.c
+@V@/bfd/elf32-m32r.c @V@/bfd/em32r.c
@V@/bfd/elf32-m68hc11.c @V@/bfd/em68hc11.c
@V@/bfd/elf32-m68hc12.c @V@/bfd/em68hc12.c
@V@/bfd/elf32-m68hc1x.c @V@/bfd/em68hc1x.c
@@ -72,6 +76,7 @@
@V@/gdb/ChangeLog-2002 @V@/gdb/ChangeLog.002
@V@/gdb/ChangeLog-2003 @V@/gdb/ChangeLog.003
@V@/gdb/ChangeLog-2004 @V@/gdb/ChangeLog.004
+@V@/gdb/ChangeLog-2005 @V@/gdb/ChangeLog.005
@V@/gdb/ChangeLog-3.x @V@/gdb/ChangeLog.3-x
@V@/gdb/ada-exp.tab.c @V@/gdb/ada-exp_tab.c
@V@/gdb/amd64fbsd-nat.c @V@/gdb/a64fb-nat.c
@@ -165,6 +170,7 @@
@V@/gdb/mipsnbsd-tdep.c @V@/gdb/mipsnbtdep.c
@V@/gdb/mips64obsd-nat.c @V@/gdb/mipsobnat.c
@V@/gdb/mips64obsd-tdep.c @V@/gdb/mipsobtdep.c
+@V@/gdb/mn10300-linux-tdep.c @V@/gdb/mn10300linux-tdep.c
@V@/gdb/ns32knbsd-nat.c @V@/gdb/ns32nb-nat.c
@V@/gdb/ns32knbsd-tdep.c @V@/gdb/ns32nb-tdep.c
@V@/gdb/objc-exp.tab.c @V@/gdb/objc-exp_tab.c
@@ -288,6 +294,8 @@
@V@/opcodes/ChangeLog-9899 @V@/opcodes/ChangeLog.9899
@V@/opcodes/ChangeLog-0001 @V@/opcodes/ChangeLog.0001
@V@/opcodes/ChangeLog-0203 @V@/opcodes/ChangeLog.0203
+@V@/opcodes/ChangeLog-2004 @V@/opcodes/ChangeLog.004
+@V@/opcodes/ChangeLog-2005 @V@/opcodes/ChangeLog.005
@V@/opcodes/ia64-opc-a.c @V@/opcodes/ia64opca.c
@V@/opcodes/ia64-opc-b.c @V@/opcodes/ia64opcb.c
@V@/opcodes/ia64-opc-d.c @V@/opcodes/ia64opcd.c
@@ -371,6 +379,24 @@
@V@/sim/testsuite/sim/arm/misaligned1.ms @V@/sim/testsuite/sim/arm/mis1.ms
@V@/sim/testsuite/sim/arm/misaligned2.ms @V@/sim/testsuite/sim/arm/mis2.ms
@V@/sim/testsuite/sim/arm/misaligned3.ms @V@/sim/testsuite/sim/arm/mis3.ms
+@V@/sim/testsuite/sim/cris/asm/tjmpsrv32-2.ms @V@/sim/testsuite/sim/cris/tjmp32-2.ms
+@V@/sim/testsuite/sim/cris/asm/tjmpsrv32.ms @V@/sim/testsuite/sim/cris/tjmp32.ms
+@V@/sim/testsuite/sim/cris/c/ftruncate1.c @V@/sim/testsuite/sim/cris/ftrunc1.c
+@V@/sim/testsuite/sim/cris/c/ftruncate2.c @V@/sim/testsuite/sim/cris/ftrunc2.c
+@V@/sim/testsuite/sim/cris/c/readlink1.c @V@/sim/testsuite/sim/cris/rdlink1.c
+@V@/sim/testsuite/sim/cris/c/readlink2.c @V@/sim/testsuite/sim/cris/rdlink2.c
+@V@/sim/testsuite/sim/cris/c/readlink3.c @V@/sim/testsuite/sim/cris/rdlink3.c
+@V@/sim/testsuite/sim/cris/c/readlink4.c @V@/sim/testsuite/sim/cris/rdlink4.c
+@V@/sim/testsuite/sim/cris/c/readlink5.c @V@/sim/testsuite/sim/cris/rdlink5.c
+@V@/sim/testsuite/sim/cris/c/readlink6.c @V@/sim/testsuite/sim/cris/rdlink6.c
+@V@/sim/testsuite/sim/cris/c/readlink7.c @V@/sim/testsuite/sim/cris/rdlink7.c
+@V@/sim/testsuite/sim/cris/c/readlink8.c @V@/sim/testsuite/sim/cris/rdlink8.c
+@V@/sim/testsuite/sim/cris/c/readlink9.c @V@/sim/testsuite/sim/cris/rdlink9.c
+@V@/sim/testsuite/sim/cris/c/readlink10.c @V@/sim/testsuite/sim/cris/rdlink10.c
+@V@/sim/testsuite/sim/cris/c/sigreturn1.c @V@/sim/testsuite/sim/cris/sigret1.c
+@V@/sim/testsuite/sim/cris/c/sigreturn2.c @V@/sim/testsuite/sim/cris/sigret2.c
+@V@/sim/testsuite/sim/cris/c/truncate1.c @V@/sim/testsuite/sim/cris/trunc1.c
+@V@/sim/testsuite/sim/cris/c/truncate2.c @V@/sim/testsuite/sim/cris/trunc2.c
@V@/sim/testsuite/sim/mips/fpu64-ps-sb1.s @V@/sim/testsuite/sim/mips/fpu64ps-sb1.s
@V@/sim/testsuite/sim/frv/interrupts/Ipipe-fr400.cgs @V@/sim/testsuite/sim/frv/interrupts/Ip-fr400.cgs
@V@/sim/testsuite/sim/frv/interrupts/Ipipe-fr500.cgs @V@/sim/testsuite/sim/frv/interrupts/Ip-fr500.cgs
next reply other threads:[~2006-01-22 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 16:28 Daniel Jacobowitz [this message]
2006-01-22 19:11 ` Eli Zaretskii
2006-01-22 20:24 ` 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=20060122162756.GA24068@nevyn.them.org \
--to=drow@false.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