(Illustration by Gaich Muramatsu)
Things that are not proper names for shared libraries are finding their way both into the link step and into the installation, see below. I suspect breakage in libtool or configure (which creates the libtool script), but have no expertise there at all. This is an old install, but a fairly recent CVS update (a week ago at most) showed the same problem with liblwp as this has with librpc2.3 (ie, no '.so' extension). It seems to work at runtime. bash-2.05b$ ldd `which clog` librpc2.3 => /usr/lib/librpc2.3 (0x40024000) liblwp.so.2 => /usr/lib/liblwp.so.2 (0x4004b000) libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7 (0x40054000) libresolv.so.2 => /lib/libresolv.so.2 (0x40145000) libc.so.6 => /lib/libc.so.6 (0x40157000) libdl.so.2 => /lib/libdl.so.2 (0x40286000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) bash-2.05b$ ls -l /usr/lib/librpc* lrwxrwxrwx 16 2003-11-17 09:37 /usr/lib/librpc2.3 -> librpc2.so.3.2.2 -rw-r--r-- 213870 2003-09-02 14:18 /usr/lib/librpc2.a -rw-r--r-- 798 2003-09-02 14:17 /usr/lib/librpc2.la lrwxrwxrwx 16 2003-09-03 08:52 /usr/lib/librpc2.so -> librpc2.so.3.2.2 lrwxrwxrwx 16 2000-10-09 19:37 /usr/lib/librpc2.so.1 -> librpc2.so.1.1.2 -rw-r--r-- 137944 2000-10-09 19:06 /usr/lib/librpc2.so.1.1.2 lrwxrwxrwx 16 2003-09-03 08:52 /usr/lib/librpc2.so.3 -> librpc2.so.3.2.2 -rw-r--r-- 147984 2003-09-02 14:18 /usr/lib/librpc2.so.3.2.2 -rw-r--r-- 36714 2003-10-27 11:34 /usr/lib/librpcsvc.a NB the link librpc2.3 used to have the same date as the other links, but I "cleaned it up" when I found it and then found myself forced to restore it. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.Received on 2003-11-17 05:20:17