Bug#231015: libm.so: symlink should be relative
At Wed, 4 Feb 2004 00:53:40 +0100,
Yann Dirson wrote:
> policy 10.5 says: "[...] symbolic links pointing from one top-level
> directory into another should be absolute."
>
> This allows me to have /usr being a symlink to a non-top-level dir, and
> having libm.so using a relative symlink breaks. This in turn causes gcc to
> pick libm.a since it can't open libm.so, and since libm.a requires libc.a as
> opposed to libc.so, I cannot link any program against libm.
Exactly.
This modification is for only debian, so I plan to put special shell
script "path-usrlib-rel2abs.sh" and use it in build.mk after installing
tmp-libc as follows:
for file in $1/*
do
if [ -L $file ];
then
newfile=`readlink $file | sed 's/\.\.\/\.\.\/lib/\/lib/'`
ln -sf $newfile $file
fi
done
debian-glibc guys, OK to commit?
Regards,
-- gotom
Reply to: