Re: other/3796: IA64 undefined references in shared libraries linked with -Bsymbolic

[wilson@gcc.gnu.org]

The following reply was made to PR other/3796; it has been noted by GNATS.

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
Cc:  
Subject: Re: other/3796: IA64 undefined references in shared libraries linked with -Bsymbolic
Date: 21 Nov 2001 06:53:16 -0000

 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