Shawn <drevil@xxxxxxxxxxxx> wrote : > On Wed, 2003-04-02 at 11:35, Jeremy Katz wrote: > > On Wed, 2003-04-02 at 11:40, Shawn wrote: > > > Yes, this problem is *very *annoying. At the moment I can't even > > > compile libneon, even with adding the correct include flags for > > > krb5.h, something about the preprocessor rejecting the file or > > > something like that. Anyway, it's very annoying that every single > > > OpenSSL package I've tried so far now needs this additional kerberos > > > stuff. I don't even use kerberos. > > > > If you use openssl, then now you use kerberos. OpenSSL 0.9.7 adds > > support for the Kerberos cipher suites in TLS (rfc 2712). > > Shouldn't autoconf or something else pick this up and add it though? Why > should everything that compiles against OpenSSL now also have to worry > about kerberos? > > Not being mean here, I just don't know how the build systems are > supposed to work... Well, I think pkgconfig is taking care of it indeed, but all programs currently building against openssl without using pkgconfig to get the compiler and ld flags need updating. Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Red Hat Linux release 8.0.9x (Phoebe) running Linux kernel 2.4.20-2.54 Load : 1.17 0.80 0.69, AC on-line, battery charging: 100% (5:39)
