> But that should be generally needed only when linking with -Wl,-z,defs ,
> without it the linker shouldn't care.
Yet using a local libc.so with the missing AS_NEEDED is a (poor) workaround.
--
Eric Botcazou
On Tue, May 20, 2014 at 01:14:24PM +0200, Eric Botcazou wrote:
> > > Yes, glibc 2.4 is required for GCC 4.9 because of this.
> >
> > Should that be noted at
> > https://gcc.gnu.org/install/specific.html#x-x-linux-gnu ?
>
> Probably, unless someone knows how to work around it. We traced it to the
> > Yes, glibc 2.4 is required for GCC 4.9 because of this.
>
> Should that be noted at
> https://gcc.gnu.org/install/specific.html#x-x-linux-gnu ?
Probably, unless someone knows how to work around it. We traced it to the
missing AS_NEEDED in /usr/lib/libc.so:
/* GNU ld script
Use the share
On 20 May 2014 11:55, Eric Botcazou wrote:
>> [snip]
>> /development/dev1/brucea/gcc4.7/bin/../lib/gcc/i686-pc-linux-gnu/4.7.0/../..
>> /../../i686-pc-linux-gnu/bin/ld: /home/brucea/gcc4 .9/lib/libmpfr.so:
>> undefined reference to symbol '___tls_get_addr@@GLIBC_2.3'
>> /development/dev1/brucea/gcc
On 20 May 2014 11:26, Bruce Adams wrote:
>
> RHEL4 (kernel 2.6.9-55.ELsmp):
>
>
> I was able to compile 4.8.1 successfully when it was released. 4.9.0 fails as
> below.
> RHEL4 is end of life (but not extended life).
>
> My feeling is this ought to work and is probably a regression I should report
> [snip]
> /development/dev1/brucea/gcc4.7/bin/../lib/gcc/i686-pc-linux-gnu/4.7.0/../..
> /../../i686-pc-linux-gnu/bin/ld: /home/brucea/gcc4 .9/lib/libmpfr.so:
> undefined reference to symbol '___tls_get_addr@@GLIBC_2.3'
> /development/dev1/brucea/gcc4.7/bin/../lib/gcc/i686-pc-linux-gnu/4.7.0/../.