From: Ken Raeburn <raeburn@cygnus.com>
To: Roland McGrath <roland@gnu.ai.mit.edu>
Cc: gas2@cygnus.com
Subject: Re: bfd assertion failed with gcc 950607
Date: Wed, 14 Jun 1995 14:37:00 -0000 [thread overview]
Message-ID: <9506142137.AA32237@cujo.cygnus.com> (raw)
In-Reply-To: <199506141651.MAA09865@churchy.gnu.ai.mit.edu>
Date: Wed, 14 Jun 1995 12:51:39 -0400
From: Roland McGrath <roland@gnu.ai.mit.edu>
> No. Solaris uses `_fooo' in foo.c. The GNU ld does the samething.
> It just complains about it.
That is contrary to the specification of the SVR4 ABI, page 4-27:
"Similarly, if a common symbol exists (i.e., a symbol whose st_shndx field
holds SHN_COMMON), the appearance of a weak symbol with the same name will
not cause an error. The link editor honors the common definition and
ignores the weak ones."
The paragraph you quote starts with "When the link editor combines
several relocatable object files...." So a shared library should be
treated like a random .o file, instead of like an archive library?
That seems counterintuitive. Is a shared library really considered a
"relocatable object file"?
The ABI description doesn't seem all that clear to me, actually. At
the start of chapter 4, it's described as a third type of object file,
distinct from relocatable files and executable files.
next prev parent reply other threads:[~1995-06-14 14:37 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
1995-06-14 9:51 ` Roland McGrath
1995-06-14 14:26 ` H.J. Lu
1995-06-14 14:37 ` Ken Raeburn [this message]
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=9506142137.AA32237@cujo.cygnus.com \
--to=raeburn@cygnus.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).