From: Andreas Schwab <schwab@suse.de>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: non-mulit-arch compiles probs
Date: Wed, 10 Apr 2002 09:50:00 -0000 [thread overview]
Message-ID: <je1ydn33c0.fsf@sykes.suse.de> (raw)
In-Reply-To: <3CB45339.2010007@cygnus.com> (Andrew Cagney's message of "Wed, 10 Apr 2002 10:59:05 -0400")
Andrew Cagney <ac131313@cygnus.com> writes:
|> Adding to the fun, I've found an entry for the ``how did this ever
|> compile'' category:
|>
|> exec.c:print_section_info (struct target_ops *t, bfd *abfd)
|> maint.c:print_section_info (const char *name, flagword flags,
|>
|> (one is static, the other has a .h declaration).
As long as the extern declaration is not visible while the static
definition is compiled, all is well.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-04-10 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 8:40 Andrew Cagney
2002-04-10 9:50 ` Andreas Schwab [this message]
2002-04-10 10:03 ` Andrew Cagney
2002-04-10 16:16 ` Michael Snyder
2002-04-10 16:23 ` 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=je1ydn33c0.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ac131313@cygnus.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