Bug#439039: libkrb5-dev: libkrb5.a missing in newer packages
Package: libkrb5-dev Version: 1.6.dfsg.1-6 Severity: important The 1.6 versions of libkrb5-dev do not include libkrb5.a. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.14.3-grsec (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libkrb5-dev depends on: ii come 2.1-1.39+1.40-WIP-2006.11.14+dfsg-2 common error description library - ii libk 1.6.dfsg.1-6MIT Kerberos administration runtim ii libk 1.6.dfsg.1-6MIT Kerberos runtime libraries libkrb5-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439039: libkrb5-dev: libkrb5.a missing in newer packages
Andrew Gray [EMAIL PROTECTED] writes: Package: libkrb5-dev Version: 1.6.dfsg.1-6 Severity: important The 1.6 versions of libkrb5-dev do not include libkrb5.a. Upstream no longer supports static linking and it's not possible to build static libkrb5 libraries. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439039: libkrb5-dev: libkrb5.a missing in newer packages
Andrew == Andrew Gray [EMAIL PROTECTED] writes: Andrew Package: libkrb5-dev Version: 1.6.dfsg.1-6 Severity: Andrew important Andrew The 1.6 versions of libkrb5-dev do not include libkrb5.a. Yes. It's going to be really challenging to fix this. Upstream basically does not support building static libraries and depends on plugins. It's not entirely clear how the plugins would be able to get to symbols in libkrb5.a if it were provided. --Sam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#439039: libkrb5-dev: libkrb5.a missing in newer packages
Sam Hartman [EMAIL PROTECTED] wrote on 08/21/2007 01:48:59 PM: Andrew Package: libkrb5-dev Version: 1.6.dfsg.1-6 Severity: Andrew important Andrew The 1.6 versions of libkrb5-dev do not include libkrb5.a. Yes. It's going to be really challenging to fix this. Upstream basically does not support building static libraries and depends on plugins. It's not entirely clear how the plugins would be able to get to symbols in libkrb5.a if it were provided. --Sam Yikes, this is going to be a problem - we just tripped over it with a seperate project because libpq5 has a dependency on libkrb53 = 1.6.dfsg.1, and we need to static link that, but libpq5.a requires libkrb5.a... Maybe a libkrb53-static package kept at the older revision where static linking worked could be made? (Tacky, but...) There's an environment variable that can be set (export krb5_force_static=yes) that does force a libkrb5.a out, but anything with 'force' in the name is most likely not a great idea. I also cannot attest to if the resulting library works (we don't use krb5 at all, but my instincts says it won't if it's trying to use these dynamic plugins), and it doesn't link (not surprisingly) anyway.
Bug#439039: libkrb5-dev: libkrb5.a missing in newer packages
[EMAIL PROTECTED] writes: Yikes, this is going to be a problem - we just tripped over it with a seperate project because libpq5 has a dependency on libkrb53 = 1.6.dfsg.1, and we need to static link that, but libpq5.a requires libkrb5.a... Maybe a libkrb53-static package kept at the older revision where static linking worked could be made? (Tacky, but...) We're going to get into trouble with security support there in the long run, which for Kerberos libraries doesn't seem like a good idea (even though the Kerberos libraries themselves rarely have security issues). Also, shipping a static library that's not compatible with the shared library seems like a bad idea. There's an environment variable that can be set (export krb5_force_static=yes) that does force a libkrb5.a out, but anything with 'force' in the name is most likely not a great idea. I also cannot attest to if the resulting library works (we don't use krb5 at all, but my instincts says it won't if it's trying to use these dynamic plugins), and it doesn't link (not surprisingly) anyway. I'm fairly sure it doesn't work. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
