From: Robert Lipe <robertlipe@usa.net>
To: + + <wrobbie@my-deja.com>
Cc: egcs@egcs.cygnus.com
Subject: Re: GCC 2.95.1 static string won't compile on SCO-OSR5
Date: Fri, 10 Sep 1999 22:08:00 -0000 [thread overview]
Message-ID: <19990910210149.A885@rjlaptop.sco.com> (raw)
In-Reply-To: <EFLIHNIHIHNOGAAA@my-deja.com>
> >This is a known (sigh) problem with current g++ and essentially all
> >the System V linkers.
>
> >But the good news is that other than templates, things work OK. :-(
>
> Hmm. Oh well, at least if I know it won't work, I can work around it.
> But could you tell me what exactly I can't do? A static 'list <int>'
> or whatever seems to work fine. What's special about a string?
I can't tell you at a C++ level (I speak only kindergarten C++) exactly
what triggers this though it seems to be template related. At the linker
level, the conflict is that the System V linkers don't allow a strong
definition to follow a weak definition of a symbol in archives and the
G++ template logic depends on the GNU ld behaviour of allowing this.
There are threads in the archives describing this in painful detail.
WARNING: multiple messages have this Message-ID
From: Robert Lipe <robertlipe@usa.net>
To: + + <wrobbie@my-deja.com>
Cc: egcs@egcs.cygnus.com
Subject: Re: GCC 2.95.1 static string won't compile on SCO-OSR5
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <19990910210149.A885@rjlaptop.sco.com> (raw)
Message-ID: <19990930180200.5kOi0M1pSyAdcYByX1_4BRJg41sSD5ZEYaFsKBucIW4@z> (raw)
In-Reply-To: <EFLIHNIHIHNOGAAA@my-deja.com>
> >This is a known (sigh) problem with current g++ and essentially all
> >the System V linkers.
>
> >But the good news is that other than templates, things work OK. :-(
>
> Hmm. Oh well, at least if I know it won't work, I can work around it.
> But could you tell me what exactly I can't do? A static 'list <int>'
> or whatever seems to work fine. What's special about a string?
I can't tell you at a C++ level (I speak only kindergarten C++) exactly
what triggers this though it seems to be template related. At the linker
level, the conflict is that the System V linkers don't allow a strong
definition to follow a weak definition of a symbol in archives and the
G++ template logic depends on the GNU ld behaviour of allowing this.
There are threads in the archives describing this in painful detail.
next prev parent reply other threads:[~1999-09-10 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-09 19:48 + +
1999-09-10 22:08 ` Robert Lipe [this message]
1999-09-30 18:02 ` Robert Lipe
1999-09-30 18:02 ` + +
-- strict thread matches above, loose matches on Subject: below --
1999-09-08 23:27 + +
1999-09-09 8:12 ` Robert Lipe
1999-09-30 18:02 ` Robert Lipe
1999-09-30 18:02 ` + +
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=19990910210149.A885@rjlaptop.sco.com \
--to=robertlipe@usa.net \
--cc=egcs@egcs.cygnus.com \
--cc=wrobbie@my-deja.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).