[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]
