Bug#378210: Miscompiles on amd64 with rpath /usr/lib64
Package: libarpack++2
Version: 2.2-3
Severity: serious
Hi,
I noticed that libarpack2 on amd64 misses most of its depends entries
because it uses the wrong path for libraries:
ql-dev:/scratch/build/sarge-biarch/arpack++/arpack++-2.2# ldd
debian/libarpack++2/usr/lib/libarpack++.so.2
libarpack.so.2 => /usr/lib64/libarpack.so.2 (0x00002aaaaabb0000)
liblapack.so.3 => /usr/lib64/liblapack.so.3 (0x00002aaaaacfa000)
libblas.so.2 => /usr/lib64/libblas.so.2 (0x00002aaaab4a3000)
libg2c.so.0 => /usr/lib64/libg2c.so.0 (0x00002aaaab60d000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x00002aaaab72f000)
libm.so.6 => /lib/libm.so.6 (0x00002aaaab911000)
libc.so.6 => /lib/libc.so.6 (0x00002aaaaba98000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaabcd7000)
libblas.so.3 => /usr/lib64/libblas.so.3 (0x00002aaaabde4000)
/lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
This confuse dpkg in sarge since it does not canonify links like
etch/sid does.
dh_shlibdeps -L libarpack++ -l debian/libarpack++2/usr/lib
dpkg-shlibdeps: warning: could not find any packages for /usr/lib64/libarpack.so.2 (libarpack.so.2)
dpkg-shlibdeps: warning: unable to find dependency information for shared library libarpack (soname 2, path /usr/lib64/libarpack.so.2, dependency field Depends)
dpkg-shlibdeps: warning: could not find any packages for /usr/lib64/liblapack.so.3 (liblapack.so.3)
...
It would be nice if this could be fixed in sarge R3 or
amd64.debian.net's stinkypete.
This bug is also present in sid (the -L /usr/lib/../lib64 and similar
entries when linking) but dpkg works around that so it has no serious
consequence [i.e. it is only serious in sarge].
MfG
Goswin
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-frosties-2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Reply to: