argus with sasl2 installation

Carter Bullard carter at qosient.com
Thu Mar 22 23:25:37 EDT 2007


Hmmm, the patch was just for the clients, and everyone was saying
that argus itself was good to go?  Did you change systems?  Was
it ever working?

Carter


On Mar 22, 2007, at 10:47 PM, Peter Van Epp wrote:

> On Thu, Mar 22, 2007 at 02:09:19PM -0400, Carter Bullard wrote:
>> Hey Mick,
>> Stupid, stupid, stupid.  I guess that's what I get for doing this
>> stuff at 1am.
>> Simple change in the configure.in file.  Here is the patch to  
>> solve all
>> problems (that you have reported :o)
>>
>> Apply patch, and then type:
>>    % autoconf
>>    %./configure --with-sasl=/usr/local
>>
>> If autoconf complains, probably just need to change the permissions
>> on the ./configure file (its output) to:
>>    % chmod u+w ./configure
>>
>> Carter
>>
>> *** configure.in.orig   Thu Mar 22 14:06:21 2007
>> --- configure.in        Thu Mar 22 14:06:36 2007
>> ***************
>> *** 140,146 ****
>>   AC_LBL_DEVEL(V_CCOPT)
>>   AC_QOSIENT_DEBUG(V_CCOPT)
>>
>> ! CMU_SASL2
>>
>>   AC_SYS_LARGEFILE
>>   AC_QOSIENT_MEMORY
>> --- 140,146 ----
>>   AC_LBL_DEVEL(V_CCOPT)
>>   AC_QOSIENT_DEBUG(V_CCOPT)
>>
>> ! CMU_SASL2(V_INCLS)
>>
>>   AC_SYS_LARGEFILE
>>   AC_QOSIENT_MEMORY
>
> 	Still no go, just fetched argus-3.0.0.0.rc.42 with this patch applied
> and autoconfig run (on FreeBSD 6.1) dies apparantly here:
>
> test5# ./configure --with-sasl=/usr/local
> ...
> checking for sasl/saslutil.h... yes
> checking for prop_get in -lsasl2... no
> configure: error: sasl2 not found. see the INSTALL for more info
>
>
> test5# vi config.log
> ...
> configure:7756: checking for sasl/saslutil.h
> configure:7763: result: yes
> configure:7768: checking for prop_get in -lsasl2
> configure:7798: gcc -o conftest -g -O2  -I/usr/local/include  -L/ 
> usr/local/lib c
> onftest.c -lsasl2  /usr/local/lib >&5
> /usr/local/lib: file not recognized: File format not recognized
>
> changing line 7774 of configure from
>
> LIBS="-lsasl2 $LIBS"
>
> to
>
> LIBS="-lsasl2 "
>
> helps that but breaks pcap later:
>
> checking sasl/saslutil.h usability... yes
> checking sasl/saslutil.h presence... yes
> checking for sasl/saslutil.h... yes
> checking for prop_get in -lsasl2... yes
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for _LARGE_FILES value needed for large files... no
> checking for local pcap library... not found
> checking for main in -lpcap... no
>
> so as usual on configure errors, I don't know :-) Hopefully this  
> suggests
> something to you though.
>
> Peter Van Epp / Operations and Technical Support
> Simon Fraser University, Burnaby, B.C. Canada
>



More information about the argus mailing list