public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: wilson@gcc.gnu.org
To: W.Stuehlmeyer@t-online.de, gcc-bugs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	wilson@gcc.gnu.org
Subject: Re: other/3796: IA64 undefined references in shared libraries linked with -Bsymbolic
Date: Fri, 16 Nov 2001 09:26:00 -0000	[thread overview]
Message-ID: <20011121065316.22046.qmail@sourceware.cygnus.com> (raw)

Synopsis: IA64 undefined references in shared libraries linked with -Bsymbolic

Responsible-Changed-From-To: unassigned->wilson
Responsible-Changed-By: wilson
Responsible-Changed-When: Tue Nov 20 22:53:16 2001
Responsible-Changed-Why:
    IA-64 maintainer
State-Changed-From-To: open->closed
State-Changed-By: wilson
State-Changed-When: Tue Nov 20 22:53:16 2001
State-Changed-Why:
    For IA-64, gcc 3.0.1 is not ABI compatible with gcc 3.0.
    Likewise, gcc 3.0.2 is not ABI compatible with 3.0.1.
    IA-64 gcc development was not finished before the gcc3
    release process started, so our choice was to tell everybody
    not to use GCC3, or to try to finish it during the gcc3
    release process and warn people about ABI compatibilities.
    We choose the latter approach.
    
    I don't have a copy of the SuSE OS release, but it sounds
    like it was built using gcc-3.0.  Thus gcc-3.0.1 is not
    supported on this system.  It will work most of the time,
    but it will fail in some cases when trying to link gcc-3.0
    compiled shared libraries into gcc-3.0.1 compiled
    applications.  That is exactly the problem you ran into.
    The only good solution is to recompile all system libraries
    (e.g. glibc) with gcc-3.0.1, but that will be difficult and
    time consuming.  It is probably better to not use 3.0.1,
    or wait for a new OS release built using a later compiler.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=3796&database=gcc


             reply	other threads:[~2001-11-21  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16  9:26 wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-16  9:29 wilson
2001-07-24 11:06 W.Stuehlmeyer

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=20011121065316.22046.qmail@sourceware.cygnus.com \
    --to=wilson@gcc.gnu.org \
    --cc=W.Stuehlmeyer@t-online.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).