[usocket-devel] Compile failure on CLISP 2.46

[Chun Tian (binghe)]

在 2008-10-1，15:24， Leslie P. Polzer 写道：

>
>>> So the libc6 statement would work for 99% of UNIX users
>>
>> Unix or Linux? What statement would we need on Solaris/ *BSD?
>
> I don't have boxes to check on, but I suppose libc6.so is pretty
> safe for UNIX.

No. libc.so.6 just for Linux, I think it means the 6th big revision  
(with incompatible API changes) of the GNU C Library.

On Solaris (I have some Solaris 10 (both SPARC and x86) boxes),  
there's no libc.so.6 but libc.so.1:

binghe at sparc-1:/usr/lib$ ls -l libc.so*
lrwxrwxrwx   1 root     root          19 Aug  4 17:16 libc.so -> ../../ 
lib/libc.so.1
lrwxrwxrwx   1 root     root          19 Aug  4 17:16 libc.so.1 - 
 > ../../lib/libc.so.1

binghe at sparc-1:/usr/lib$ ldd /bin/ls
         libsec.so.1 =>   /lib/libsec.so.1
         libc.so.1 =>     /lib/libc.so.1
         libavl.so.1 =>   /lib/libavl.so.1
         libm.so.2 =>     /lib/libm.so.2
         /platform/SUNW,Ultra-80/lib/libc_psr.so.1

And on FreeBSD (which I don't have a running one), since they also do  
not use GNU C Library either, it's quite possible that the libc.so  
revision isn't "6" too.

But, on all UNIX, I think the file "/usr/lib/libc.so" will be the  
right answer.

--
Chun Tian (binghe)