Subject: Strange things (libc.so.12.17)
To: None <current-users@NetBSD.ORG>
From: None <apr@spade.apc.aip.de>
List: current-users
Date: 08/05/1997 21:38:36
-----BEGIN PGP SIGNED MESSAGE-----

Hi,

this is mostly from memory - I have not handy my NetBSD/pmax system:

I tried to compile a current-kernel (based on sup approx. 30/7) on a
system running 1.2G (I follow the -current tightly).
This fails in linking with lots of undefined references to strncpy.

OK.

So I try a make build.
Everything is fine till it comes to libc.
It compiles and installs including libc.so.12.17.
Then make failes with core dumps.

Investigation shows: Everything is fine with 12.16 when libc.so and
libc.so.12 point to it -  BUT ONLY if NO FILE libc.so.12.17 EXISTS -
i.e. despite the fact the the links point to 12.16 the pure existence
of a libc.so.12.17 makes shared executables fail.
This is true even with or without a new ldconfig or a reboot!
(Several single or multi-users tries!)
Only a rename of libc.so.12.17 to something out of the naming scheme
(e.g. _libc.so.12.17) will help!

Who will enlighten me???

TIA Andreas

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQBVAwUBM+eBOedLRUEjDVTxAQGGEQH/fonX1Jc+XFCgyygOBMPnnk9YjOqj9bZM
L0ItpIRPS9HWYYsRY8szgZMmLpJr/Mc/KGV/yYX9rojnn8Sd2k9oxg==
=mmW6
-----END PGP SIGNATURE-----