rc41 and sasl

Carter Bullard carter at qosient.com
Tue Mar 13 12:53:28 EDT 2007


Please, tweak away, I will incorporate whatever works, as long as it
doesn't break anything else.   We do have/have had cyrus people, or
at least CMU people, on the list, maybe they can chime in?

Carter


On Mar 13, 2007, at 12:25 PM, Michael Hornung wrote:

> I've noticed that SASL support is hard to build in by default.  On  
> a FC6 x86 Linux box I have the following installed:
>
> cyrus-sasl-lib-2.1.22-4
> cyrus-sasl-2.1.22-4
> cyrus-sasl-plain-2.1.22-4
> cyrus-sasl-devel-2.1.22-4
>
> and they put headers in /usr/include/sasl/ and the library is  
> libsasl2.a.  The rc41 client and server configuration does not  
> allow one to specify "/usr/include/sasl/" as the includedir since  
> it appends "include" to whatever you supply with "--with-sasl".   
> And the test for libsasl does not look for -lsasl2!
>
> Similar for OpenBSD 4.0 with the cyrus-sasl-2.1.21p2 package  
> installed. The library is libsasl2 (whereas building argus looks  
> for libsasl) and the includes are in include/sasl/.
>
> I could probably tweak the build process, but if cyrus-sasl  
> popularly uses this naming scheme, perhaps the build scripts should  
> check for those files from the get-go?
>
> -Mike
>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20070313/e9334902/attachment.html>


More information about the argus mailing list