Re: version `GLIBC_2.14' not found (required by build/genhooks) ‏

[Mikael Morin <mikael.morin@sfr.fr>]

On Thursday 22 September 2011 11:56:12 Teodori Serge wrote:
> Hello,
> I'm building a toolchain in /opt dir. I have already build and installed
> glibc-2.14 and binutils-2.21.1a in /opt.
> Now I want to build and install gcc-4.6.1 with gmp, mpfr and mpc also in
> /opt.
> 
> Here is my configure:
> 
> ../gcc-4.6.1/configure --prefix=/tools --disable-nls --disable-shared
> --disable-multilib --disable-decimal-float --disable-threads
> --disable-libmudflap --disable-libssp --disable-libgomp
> --disable-libquadmath --disable-target-libiberty --disable-target-zlib
> --enable-languages=c --without-ppl --without-cloog
> 
> Here is the last output of my build:
> 
> build/genhooks > tmp-target-hooks-def.h
> build/genhooks: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14'
> not found (required by build/genhooks)
> make[3]: *** [s-target-hooks-def-h] Error 1
> make[3]: *** Waiting for unfinished jobs....
> rm gcc.pod
> make[3]: Leaving directory `/home/serge/Documents/gcc-build/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory `/home/serge/Documents/gcc-build'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory `/home/serge/Documents/gcc-build'
> make: *** [all] Error 2
> 
> The problem is very obvious, gcc build is not taking the toolchain
> glibc-2.14 in /opt/lib but it is taking the one the host uses which is
> eglibc-2.13 in /usr/lib.
> I set various flags to the linker and compiler, they are all looking in
> the right directory. It must be something in the configure script?
> Can anyone help me please.
> Thank you
It seems the generated program genhooks is correctly linked to your new glibc.
However, you need to either set LD_LIBRARY_PATH or change the /etc/ld.so.conf 
configuration file so that genhooks loads the right library when it is 
executed.

Mikael.

PS: this list is for the automatic messages generated by the bug tracking 
system at http://gcc.gnu.org/bugzilla. For questions, you should use the
gcc-help mailing list.