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.
