found something! (was: something wrong with glibc?)
> > > make[1]: Entering directory `/usr/src/linux-2.4.18/scripts/lxdialog'
> > > /lib/libc.so.6: undefined reference to
> > > `_dl_lookup_versioned_symbol_skip@GLIBC_PRIVATE'
> > > /lib/libc.so.6: undefined reference to `_rtld_global@GLIBC_PRIVATE'
> > > /lib/libc.so.6: undefined reference to
> > > `_dl_lookup_versioned_symbol@GLIBC_PRIVATE'
> > > /lib/libc.so.6: undefined reference to
`_dl_start_profile@GLIBC_PRIVATE'
> > > /lib/libc.so.6: undefined reference to
`_dl_check_map_versions@GLIBC_PRIVATE'
> > > /lib/libc.so.6: undefined reference to
`__libc_enable_secure@GLIBC_PRIVATE'
> >
> > I have seen this before. Please look at
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171778 and help to
> > solve it.
>
> I experience exactly the same error messages while compiling cups-1.1.18
> on RedHat 8.1, kernel 2.4.20, gcc 3.2.2.
> ...
I did a dilligent analysis of my system and found something that might be of
importance.
I wrote a script that reports me any file dublicate on my system and it told
me
that I have 4 versions of libc.so.6:
lrwxrwxrwx 1 root root 14 Jan 20 15:58 /lib/libc.so.6 ->
libc-2.2.93.so
lrwxrwxrwx 1 root root 14 Jan 20 15:58
/usr/lib/i686/libc.so.6 -> libc-2.2.93.so
lrwxrwxrwx 1 root root 13 Mar 3 21:21
/usr/lib/libc.so.6 -> libc-2.2.4.so
lrwxrwxrwx 1 root root 14 Jan 20 16:13
/var/ftp/lib/libc.so.6 -> libc-2.2.93.so
and for whatever reasons one of them point to an older libc version.
I would like to correct that but this is something that kind of scares me.
I remember exactly that I ones crashed my entire system by accidentally
deleting the libc.
What I tried now was forcing a symbolic link to the new version:
ln -sf /lib/libc-2.2.93.so /usr/lib/libc.so.6
That works, but when I do an `ldconfig` afterward it points to the old
version again.
Question #1: Could that weird link cause the compilation error?
Question #2: How do I correct the unwanted link without jeopardizing my
system?
Thanks for any help,
-- Bernd
Reply to: