Bug#231015: libm.so: symlink should be relative
Package: libc6
Version: 2.3.2.ds1-11
Severity: serious
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.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bylbo 2.4.23-k6+preempt+acl #1 sam déc 13 00:48:10 CET 2003 i586
Locale: LANG=français, LC_CTYPE=français
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-7 The Berkeley database routines [gl
-- no debconf information
--
Yann Dirson <ydirson@altern.org> | Why make M$-Bill richer & richer ?
Debian-related: <dirson@debian.org> | Support Debian GNU/Linux:
Pro: <yann.dirson@fr.alcove.com> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>
Reply to: