Re: Not everyone is linking shared libraries to libc

[William Lee Irwin III <wli@holomorphy.com>]

Previously Wichert Akkerman wrote:
>> Can people please run the attached script on their system and see if it
>> finds more broken packages on their system?

On Fri, Feb 23, 2001 at 06:01:59PM +0100, Wichert Akkerman wrote:
> The attached script had a slight typo, new version attached.

@ dpkg --list | wc -l
   1726

Now for the results of the script:

@ ./check-libc|& tee -a libc.chk
objdump: /usr/lib/libc.so: File format not recognized
/lib/libc.so.5.4.46 is not linked to libc
/lib/ld.so.1.9.11 is not linked to libc
/lib/libc-2.2.1.so is not linked to libc
/lib/libm.so.5.0.9 is not linked to libc
/lib/ld-2.2.1.so is not linked to libc
/lib/ld.so is not linked to libc
/lib/ld-linux.so.1.9.11 is not linked to libc
/usr/lib/libplc4.so is not linked to libc
/usr/lib/libplds4.so is not linked to libc
/usr/lib/libc.so is not linked to libc

I have no idea what it was, but something put /usr/lib/libc.so there,
and it wasn't me. It's a text file with the following contents:

/* GNU ld script
   Use the shared library, but some functions are only in
   the static library, so try that secondarily.  */
GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )

Kudos to whoever can find where it came from.


Cheers,
Bill