Package: libpam0g-dev Version: 1.1.3-3 Severity: grave Justification: renders package unusable
1.1.3-3 changed the install rules so that the *.a files for libpam are now installed in the multiarch path, but the *.so files are still installed in /usr/lib. The linker search uses the first library that it finds and the multiarch path is earlier than /usr/lib in the search order. This means that any software building against PAM will end up building against the static libraries instead of the shared libraries because the static libraries are earlier on the search path and there are no *.so links in the same directory. This, among other things, will cause a FTBFS for all PAM modules on platforms where shared module code has to be built PIC. See the build logs for libpam-krb5, for example. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam0g-dev depends on: ii libc6-dev [libc-dev] 2.13-21 ii libpam0g 1.1.3-3 libpam0g-dev recommends no packages. libpam0g-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
