From: hjl@nynexst.com (H.J. Lu)
To: roland@gnu.ai.mit.edu (Roland McGrath)
Cc: gas2@cygnus.com
Subject: Re: bfd assertion failed with gcc 950607
Date: Wed, 14 Jun 1995 09:43:00 -0000 [thread overview]
Message-ID: <9506141636.AA11264@titanic.nynexst.com> (raw)
In-Reply-To: <199506141608.MAA09776@churchy.gnu.ai.mit.edu>
>
> I am certain that your test case is a valid program and that the references
> to `fooo' in junk.c should resolve to the common defn in fred.c rather than
> to `_fooo' in foo.c.
No. Solaris uses `_fooo' in foo.c. The GNU ld does the samething.
It just complains about it.
>
> So if that is what your patches accomplish, I would say they might be
No, my patches only turn off the complaints.
> right. I don't think there is anyone available this month who really
> understands ld well enough to be sure if that is the best way to fix it.
>
--
H.J. Lu
NYNEX Science and Technology, Inc. hjl@nynexst.com
next prev parent reply other threads:[~1995-06-14 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18151.9506140906@afs.mcc.ac.uk>
1995-06-14 7:05 ` H.J. Lu
1995-06-14 9:08 ` Roland McGrath
1995-06-14 9:43 ` H.J. Lu [this message]
1995-06-14 9:51 ` Roland McGrath
1995-06-14 14:26 ` H.J. Lu
1995-06-14 14:37 ` Ken Raeburn
1995-06-14 15:17 ` H.J. Lu
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=9506141636.AA11264@titanic.nynexst.com \
--to=hjl@nynexst.com \
--cc=gas2@cygnus.com \
--cc=roland@gnu.ai.mit.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).