From: Albert Chin <gcc@lists.thewrittenword.com>
To: gcc@gcc.gnu.org
Subject: Re: Building LyX 1.2.0 on HP-UX 11.11 with G++ 3.2
Date: Fri, 23 Aug 2002 05:32:00 -0000 [thread overview]
Message-ID: <20020823073245.A35095@oolong.il.thewrittenword.com> (raw)
In-Reply-To: <200208222338.g7MNcuL12177@porcupine.slc.redhat.com>
On Thu, Aug 22, 2002 at 05:38:56PM -0600, Jeff Law wrote:
> In message < 200208222245.g7MMjAXl007183@hiauly1.hia.nrc.ca >, "John David Anglin
> " writes:
> >> 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.
> >
> >It's not obvious that the primary needs to be external. I am looking
> >at map_secondary_to_primary in fixups.c. If it needs to be external,
> >could it be hidden?
> I hadn't thought about trying to tweak the hidden bit for the primary.
> It's definitely worth a try -- the lack of weak symbol support is a major
> problem on this platform so it's worth some effort to try and make
> secondary definitions act like weak symbols.
Does HP-UX handle C++ code with templates well (by "well" I mean as
"well" as on Solaris or Tru64 UNIX or IRIX)? The problems we're
running into have to do with template code.
--
albert chin (china@thewrittenword.com)
next prev parent reply other threads:[~2002-08-23 5:32 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
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 [this message]
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=20020823073245.A35095@oolong.il.thewrittenword.com \
--to=gcc@lists.thewrittenword.com \
--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).