Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Build with Kerberos v5 / OpenSSL and CURRENT (Julien ?LIE)


----------------------------------------------------------------------

Message: 1
Date: Sat, 26 Oct 2013 19:11:53 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Build with Kerberos v5 / OpenSSL and CURRENT
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi all,

If you are using CURRENT (2.6.0) with Kerberos v5 support, please note 
that the --with-kerberos configure flag has been renamed to --with-krb5 
so you should now use this new flag, if needed.

Also note that new --with-krb5-include and --with-krb5-lib configure 
flags have been added so as to mention non-standard paths.

Same thing for OpenSSL:  --with-openssl-include and --with-openssl-lib 
configure flags have been added.


Another change:
If the Kerberos v5, or OpenSSL SSL and crypto libraries are found at 
configure time, INN will now be built with support for them unless 
respectively the --without-krb5, or --without-openssl flags are 
explicitly passed to configure.



If you notice anything suspicious during your builds of CURRENT with 
Kerberos v5 or OpenSSL, please report the issue you are facing.

-- 
Julien ?LIE

? Vinum nouum, amicus nouus : uesterascet, et cum suauitate bibes
   illud. ?


------------------------------

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

End of inn-workers Digest, Vol 56, Issue 1
******************************************

Reply via email to