cvs commit: src/share/mk bsd.lib.mk

[David O'Brien]

On Thu, Sep 04, 2003 at 09:58:39PM +0300, Ruslan Ermilov wrote:
> Linux looks things up in both /lib and
> /usr/lib, and does not have symlinks from /usr/lib to /lib.

uh?
    suse# cat /usr/lib/libc.so
        /* 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 )
    suse# ls /lib/libc.* /usr/lib/libc.*
    /lib/libc.so.6*  /usr/lib/libc.a  /usr/lib/libc.so



> The only reason while I still think we should support both
> /lib and /usr/lib in cc(1) and ld(1) by default is to allow
> our users to have /usr symlinked somethere, otherwise relative
> symlinking from /usr/lib to ../../lib does not work, and we
> are back to that endless thread.  BTW, NetBSD uses absolute
> paths in symlinks from /usr/lib to /lib:
> 
> > ls -l /usr/lib/libz.so*
> lrwxr-xr-x  1 root  wheel     16 Aug 30 14:58 /usr/lib/libz.so -> /lib/libz.so.0.3
> lrwxr-xr-x  1 root  wheel     16 Aug 30 14:58 /usr/lib/libz.so.0 -> /lib/libz.so.0.3
> lrwxr-xr-x  1 root  wheel     16 Aug 30 14:58 /usr/lib/libz.so.0.3 -> /lib/libz.so.0.3

I think we should also -- one does not care about the .so links when
running single user with / mounted elsewhere.