From: Jeff Law <law@porcupine.slc.redhat.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: gcc@gcc.gnu.org
Subject: Re: Building LyX 1.2.0 on HP-UX 11.11 with G++ 3.2
Date: Thu, 22 Aug 2002 15:14:00 -0000 [thread overview]
Message-ID: <200208222219.g7MMJXm11922@porcupine.slc.redhat.com> (raw)
In-Reply-To: <200208222208.g7MM8DYV007102@hiauly1.hia.nrc.ca>
In message < 200208222208.g7MM8DYV007102@hiauly1.hia.nrc.ca >, "John David
Anglin" writes:
>> Looks like they (HP) are using aborted code -- we tried to make SOM
>> secondary definitions masquerade as weak symbols, but in the end it won't
>> work due to limitations of secondary definitions. Trust me, if they're
>> emitting .weak for SOM, it's going to break -- it's just a matter of time.
>
>I thought the major issue was we weren't providing a primary symbol
>definition for the secondary. The primary symbol has to have the same
>name as the secondary with '_' prefixed. Maybe gas just needed a fix
>to do this?
But the primary symbol had to be a normal symbol with the underscore
prefix *and* with external scope. The external scope restriction
is what killed using secondary definitions to emulate weak definitions.
jeff
next prev parent reply other threads:[~2002-08-22 15:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 15:08 John David Anglin
2002-08-22 15:14 ` Jeff Law [this message]
2002-08-22 15:45 ` John David Anglin
2002-08-22 16:34 ` Jeff Law
2002-08-22 17:11 ` John David Anglin
2002-08-23 5:32 ` Albert Chin
2002-08-23 10:08 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2002-08-22 5:31 Albert Chin
2002-08-22 9:29 ` Albert Chin
2002-08-22 9:34 ` John Levon
2002-08-22 9:48 ` Albert Chin
2002-08-22 12:12 ` Jeff Law
2002-08-22 12:15 ` Albert Chin
2002-08-22 9:40 ` Jeff Law
2002-08-22 11:02 ` Albert Chin
2002-08-22 12:02 ` Jeff Law
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=200208222219.g7MMJXm11922@porcupine.slc.redhat.com \
--to=law@porcupine.slc.redhat.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).