Re: /lib symlinks problem?

On Sat, Aug 30, 2003 at 01:54:27PM +0200, Alexander Leidinger wrote:
[...]
> I think the problem is, that some tools have a problem finding it...:
> ---snip---
> (3) netchild_at_ttyp1 % nm -D /usr/lib/libc.so | grep fpcl
> nm: /usr/lib/libc.so: No such file or directory
> 
> (4) netchild_at_ttyp1 % ll /usr/lib/libc.so
> lrwxr-xr-x  1 root  wheel  19B 29 Aug 13:57 /usr/lib/libc.so_at_ -> ../../lib/libc.so.5
> 
> (5) netchild_at_ttyp1 % ll /usr 
> lrwxr-xr-x  1 root  wheel  7.0B 18 Aug  2001 /usr_at_ -> big/usr
> 
> (7) netchild_at_ttyp1 % ll /lib/libc.so 
> lrwxr-xr-x  1 root  wheel  9.0B 29 Aug 13:57 /lib/libc.so_at_ -> libc.so.5
> ---snip---
> 
> I think a workaround would be to use absolute symlinks (at least as an
> option).
> 
I might be missing an obvious, but I just don't see a reason
why we should use relative linking here: we should just link
to where we really install.  With the attached patch, I get:

$ make -n install -DNOMAN DESTDIR=/foo
install -C -o root -g wheel -m 444   libalias.a /foo/usr/lib
install -s -o root -g wheel -m 444     libalias.so.4 /foo/lib
ln -fs libalias.so.4 /foo/lib/libalias.so
ln -fs /foo/lib/libalias.so.4  /foo/usr/lib/libalias.so


Cheers,
-- 
Ruslan Ermilov		Sysadmin and DBA,
ru_at_sunbay.com		Sunbay Software Ltd,
ru_at_FreeBSD.org		FreeBSD committer