Vanuxem Grégory wrote:
>Hi, > >Le lundi 15 août 2005 à 19:21 +0400, Vitaly Fertman a écrit : > > >>ok, as we can see in config.log the problem is: >> >>/usr/bin/ld: __libc_errno: TLS definition in >>/usr/lib/gcc-lib/x86_64-linux-gnu/3.3.6/../../../../lib64/libc.a(errno.o) >>section .tbss mismatches non-TLS reference in >>/usr/lib/gcc-lib/x86_64-linux-gnu/3.3.6/../../../../lib64/libc.a(check_fds.o) >> >>/usr/lib/gcc-lib/x86_64-linux-gnu/3.3.6/../../../../lib64/libc.a: >>ne peut lire les symboles: Mauvaise valeur >> >>when we try to compile the test program. >>this message points to a problem in libc, not in libaal. >> >> >>there is a test program : /home/greg/temp/conftest.c >>I try to compile it with the same command as from the config.log, >>but not linking it to libaal: >># gcc -o conftest -O2 -march=athlon-xp -mcpu=athlon-xp -mmmx >>-msse -msse2 -mfpmath=sse -static conftest.c >> >>and get the same error message. >> >>but if I remove -static, it gets compiled successfully. >>even if I also link it to libaal -- there is a program conftest2.c, the same >>as >>the one that fails from the config.log, I run the same command as mentioned >>in config.log: >># gcc -o conftest2 -march=athlon-xp -mcpu=athlon-xp -mmmx >>-msse -msse2 -mfpmath=sse conftest2.c -laal >># <- success >> >>so the problem is related to installed libc, not to libaal. >> >> >> > >This is a known bug in glibc 2.3.2. > >I've upgraded to the glibc version 2.3.5 and >that works. > >Thanks, > > >Cheers, > >Greg > > > > > > > Vitaly, can you detect 2.3.2 and warn the user?
