Strange library dependencies after installing glibc-2.3.2

[Juergen Rose]

Hello,

until now I installed glibc-2.3.2 succesfully on three linux-2.4.20 PCs
without problems. When I repeated the procedure on the fourth PC:

../glibc-2.3.2/configure --prefix=/usr --enable-kernel=current
--enable-add-ons

'make' and 'make check' works without problems, but 'make install'
reports:

test ! -x /usr/src/Libs/glibc-build/elf/ldconfig || LC_ALL=C LANGUAGE=C
\
  /usr/src/Libs/glibc-build/elf/ldconfig  \
                               /lib /usr/lib
CC="gcc" /usr/bin/perl scripts/test-installation.pl
/usr/src/Libs/glibc-build/
Use of uninitialized value in string ne at scripts/test-installation.pl
line 163, <LDD> line 19.
Library libz is not correctly installed.
Please check your installation!
Offending line of ldd output:   libz.so.1 => /usr/lib/libz.so.1
(0x402cd000)

The script has found some problems with your installation!
Please read the FAQ and the README file and check the following:
- Did you change the gcc specs file (necessary after upgrading from
  Linux libc5)?
- Are there any symbolic links of the form libXXX.so to old libraries?
  Links like libm.so -> libm.so.5 (where libm.so.5 is an old library)
are wrong,
  libm.so should point to the newly installed glibc file - and there
should be
  only one such link (check e.g. /lib and /usr/lib)

What is that? I do not use libc.5 for more than five years. So I
thought, maybe libz-1.1.4, which I install in december, is not correct.
So I compiled once more libc. 'make install' with libz resulted in a bus
error. After that, nothing was working (no ls, no make). I found that
/usr/lib/libz.so.1.1.4 was installed but some link to libz.so or
libz.so.1 was missing. So I booted with KNOPPIX-CD, created that link.
I could boot again linux from harddisk and could login.

The gcc I used, was gcc-3.2.2, which was compiled with glibc-2.3.1,
binutils has been binutils-2.13.90.0.18 from slackware-9.0 now I
installed binutils-030402-i386-1 (repeated then the complete '/bin/rm
/usr/src/glibc-build/*'-configure-make-make-install, without any change
for glibc.

I assume, that the reason for this behaviour is, that there are now some
strange dependencies in the glibc of the affected PC, e.g. 
ldd /bin/ls gives
        /usr/X11R6/lib/libfreetype.so => /usr/X11R6/lib/libfreetype.so
(0x40015000)
        librt.so.1 => /lib/librt.so.1 (0x4007f000)
        libc.so.6 => /lib/libc.so.6 (0x40092000)
        libz.so.1 => /usr/lib/libz.so.1 (0x401c5000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x401d3000)
while on the working PC (also with glibc-2.3.2) it is
        librt.so.1 => /lib/librt.so.1 (0x40026000)
        libc.so.6 => /lib/libc.so.6 (0x40039000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x4016c000)

If I perform 'ldd /lib/libc*2.3.2*' on the system with the problems, I
get:
/lib/libc-2.3.2.so:
        /usr/X11R6/lib/libfreetype.so => /usr/X11R6/lib/libfreetype.so
(0x40015000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libz.so.1 => /usr/lib/libz.so.1 (0x4007f000)
/lib/libcrypt-2.3.2.so:
        /usr/X11R6/lib/libfreetype.so => /usr/X11R6/lib/libfreetype.so
(0x40015000)
        libc.so.6 => /lib/libc.so.6 (0x4007f000)
        libz.so.1 => /usr/lib/libz.so.1 (0x401b2000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

So the glibc depends on libfreetype and libz, which is strange.

In /etc/ld.so.conf I have:

/usr/local/lib
/usr/X11R6/lib
/usr/i386-slackware-linux/lib
/usr/lib/qt/lib

Do you have any idea for the reason of this behaviour and how to repair
the corrupted system?

        Urgently waiting for response
                Juergen

-- 
Juergen Rose <address@hidden>
Max-Delbrueck-Zentrum