public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dave.anglin@nrc.ca
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/4260: ABI change beween 3.0 and 3.0.1: programs linked with 3.0 lib don't work after 3.0.1 lib is installed
Date: Fri, 07 Sep 2001 13:16:00 -0000 [thread overview]
Message-ID: <20010907200917.14056.qmail@sourceware.cygnus.com> (raw)
>Number: 4260
>Category: libstdc++
>Synopsis: ABI change beween 3.0 and 3.0.1: programs linked with 3.0 lib don't work after 3.0.1 lib is installed
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Sep 07 13:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: John David Anglin
>Release: unknown-1.0
>Organization:
>Environment:
hppa1.1-hp-hpux10.20
>Description:
The symbol names for the libstdc++ global constructor and
destructor changed from
_GLOBAL__FI_libstdc___sl_3_0
_GLOBAL__FD_libstdc___sl_3_0
to
_GLOBAL__FI_libstdc___sl_3_1
1.
The internal name for both library versions is
`libstdc++.sl.3'. Thus, programs linked with the
3.0 library load the new 3.1 library. However,
they fail when the symbol _GLOBAL__FI_libstdc___sl_3_0
isn't found.
The same constructor/destructor names need to be used
for libraries that are supposed to compatible, and they
need to be kept in sync with the internal names used for
the library.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-09-07 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 13:16 dave.anglin [this message]
2002-02-19 18:09 bkoz
2002-02-19 19:26 John David Anglin
2002-04-04 9:58 mmitchel
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=20010907200917.14056.qmail@sourceware.cygnus.com \
--to=dave.anglin@nrc.ca \
--cc=gcc-gnats@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).