[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#236066: Forbidden relative symlink breaks package building [+ fix]

Package: libc6-dev
Version: 2.3.2.ds1-11
Severity: serious
Tags: sid


libc6-dev includes several "/usr/lib/lib*.so" files that are needed
for building packages but are, maybe accidently, relative instead of
absolute symlinks to "/lib/lib*.so.*".

This is against the "general" rule in
and due to the fact that /usr is sometimes mountet on a different
partition that / i.e. /lib and relative symlinks don't work across 
partitions (they always go relative from the absolut path i.e. you 
end up in /mnt/my_usr_and_var/ or similar and not in /)

The problem I faced now was that although the package builds fine, the
linker silently put a "TEXTREL=0x0" flag inside the shared libraries
which markes them as not "PIC" compatible although they are compiled
with "-fPIC". This does not comply with our policy as it makes programs
like e.g. prelink not working with such libraries.

The fix would be simply to replace "../.." by "/" when creating the



-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux app109 2.4.23 #1 Sat Dec 6 13:30:13 CET 2003 i686
Locale: LANG=de_DE, LC_CTYPE=de_DE (ignored: LC_ALL set)

Versions of packages libc6-dev depends on:
ii  libc6                2.3.2.ds1-11        GNU C Library: Shared libraries an
ii  linux-kernel-headers 2.5.999-test7-bk-15 Linux Kernel Headers for developme

-- no debconf information

Reply to: