From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] more all-target -Werror patches
Date: Tue, 01 Oct 2002 09:30:00 -0000 [thread overview]
Message-ID: <3D99CDB6.2030205@redhat.com> (raw)
In-Reply-To: <ro1adlyuo7v.fsf@jackfruit.Stanford.EDU>
> Here are the last patches for getting GDB to build on my machine on
> all targets with -Werror if appropriate.
>
> OK to commit? The gdb_string ones are pretty obvious; I'm not sure
> why GCC is issuing a warning on remote-sds.c that requires me to
> insert a stray semicolon to quell it, but doing so shouldn't hurt
> anything.
>
> David Carlton
> carlton@math.stanford.edu
>
> 2002-09-30 David Carlton <carlton@math.stanford.edu>
>
> * Makefile.in (ppc-sysv-tdep.o): Depend on gdb_string_h.
> * ppc-sysv-tdep.c: #include "gdb_string.h".
> * remote-sds.c (getmessage): Add semicolon after 'retry' label to
> pacify GCC.
Yes, definitly.
Andrew
> Index: Makefile.in
> ===================================================================
> RCS file: /cvs/src/src/gdb/Makefile.in,v
> retrieving revision 1.262.2.7
> diff -u -p -r1.262.2.7 Makefile.in
> --- Makefile.in 27 Sep 2002 20:03:04 -0000 1.262.2.7
> +++ Makefile.in 30 Sep 2002 18:47:59 -0000
> @@ -1978,7 +1978,7 @@ ppc-linux-tdep.o: ppc-linux-tdep.c $(def
> $(symtab_h) $(target_h) $(gdbcore_h) $(gdbcmd_h) $(symfile_h) \
> $(objfiles_h) $(regcache_h) $(value_h) $(solib_svr4_h) $(ppc_tdep_h)
> ppc-sysv-tdep.o: ppc-sysv-tdep.c $(defs_h) $(gdbcore_h) $(inferior_h) \
> - $(regcache_h) $(value_h) $(ppc_tdep_h)
> + $(regcache_h) $(value_h) $(gdb_string_h) $(ppc_tdep_h)
> ppcbug-rom.o: ppcbug-rom.c $(defs_h) $(gdbcore_h) $(target_h) $(monitor_h) \
> $(serial_h) $(regcache_h)
> ppcnbsd-nat.o: ppcnbsd-nat.c $(defs_h) $(inferior_h) $(ppc_tdep_h) \
>
> Index: ppc-sysv-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/ppc-sysv-tdep.c,v
> retrieving revision 1.1
> diff -u -p -r1.1 ppc-sysv-tdep.c
> --- ppc-sysv-tdep.c 30 May 2002 01:21:51 -0000 1.1
> +++ ppc-sysv-tdep.c 30 Sep 2002 18:48:17 -0000
> @@ -25,6 +25,7 @@
> #include "inferior.h"
> #include "regcache.h"
> #include "value.h"
> +#include "gdb_string.h"
>
> #include "ppc-tdep.h"
>
> Index: remote-sds.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/remote-sds.c,v
> retrieving revision 1.20
> diff -u -p -r1.20 remote-sds.c
> --- remote-sds.c 10 Feb 2002 04:08:42 -0000 1.20
> +++ remote-sds.c 30 Sep 2002 18:45:17 -0000
> @@ -978,6 +978,7 @@ getmessage (unsigned char *buf, int fore
> /* Try the whole thing again. */
> retry:
> /* need to do something here */
> + ;
> }
>
> /* We have tried hard enough, and just can't receive the packet. Give up. */
>
next prev parent reply other threads:[~2002-10-01 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 9:18 David Carlton
2002-10-01 9:30 ` Andrew Cagney [this message]
2002-10-01 12:29 ` David Carlton
2002-10-01 12:32 ` Michael Snyder
2002-10-01 12:37 ` Daniel Jacobowitz
2002-10-01 12:43 ` David Carlton
2002-10-01 13:15 ` David Carlton
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=3D99CDB6.2030205@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--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