From: Anthony Green <green@redhat.com>
To: gdb-patches@gcc.gnu.org
Subject: Patch: fix monitor.c build problem
Date: Mon, 22 Sep 2003 14:28:00 -0000 [thread overview]
Message-ID: <1064240932.3570.206.camel@escape> (raw)
I am unable to build monitor.c with a recent gcc because of a
conflicting targ_ops declaration (both static and extern in same
compilation unit). It looks like we can just delete the second
declaration. Ok?
2003-09-22 Anthony Green <green@redhat.com>
* monitor.c (monitor_expect): Delete unused conflicting targ_ops
declaration.
Index: gdb/monitor.c
===================================================================
RCS file: /cvs/uberbaum/gdb/monitor.c,v
retrieving revision 1.42
diff -c -u -p -r1.42 monitor.c
--- gdb/monitor.c 11 Jun 2003 13:16:28 -0000 1.42
+++ gdb/monitor.c 22 Sep 2003 14:23:57 -0000
@@ -521,7 +521,6 @@ monitor_expect (char *string, char *buf,
char *p = string;
int obuflen = buflen;
int c;
- extern struct target_ops *targ_ops;
if (monitor_debug_p)
{
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
next reply other threads:[~2003-09-22 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 14:28 Anthony Green [this message]
2003-09-22 14:44 ` Daniel Jacobowitz
2003-09-22 14:56 ` Andrew Cagney
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=1064240932.3570.206.camel@escape \
--to=green@redhat.com \
--cc=gdb-patches@gcc.gnu.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