[ARGUS] sasl a solution (ugly, but a solution :-))

[Peter Van Epp]

	After some more poking, more information. Sasl version 2 is probably
where we should be moving, but its likly 2.0.7 country. V2 is a complete change
and requires a client rewrite. It has also been stable for around a year and
thus is likely a good thing to go to.
	For 2.0.6, the following configure and configure.in patches will make
the cyrus-sasl-1.5.28.tar.gz tarball (if unpacked, built and installed and
/usr/local/lib/sasl sym linked to /usr/lib/sasl so it finds the plug ins) works
if configure --with-sasl=/usr/local is done. Unfortunatly this seems to be for
some value of "work" in that with two ra's reading different ports I get a
segfault from the sasl library. I'm currently running a single ra to a remote
host (the one that has segfaulted in the past) to see if it is two ra instances
that is causing the excitment and to see if the segfault is always the same 
(the earlier ones were from a different sasl libray and were erased with the 
library, but I think were in a different place than the current ones).

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada

*** configure.in.orig	Sun Aug 15 13:08:34 2004
--- configure.in	Sun Aug 15 13:00:10 2004
***************
*** 25,30 ****
--- 25,33 ----
  AC_LBL_DEVEL(V_CCOPT)
  AC_QOSIENT_DEBUG(V_CCOPT)
  AC_CMU_SASL
+ if test "$SASLFLAGS" != ""; then
+ 	V_INCLS="$V_INCLS $SASLFLAGS"
+ fi
  AC_SYS_LARGEFILE
  
  umask 002


*** configure.orig	Sun Aug 15 13:00:53 2004
--- configure	Sun Aug 15 13:01:37 2004
***************
*** 4250,4255 ****
--- 4250,4258 ----
        fi
     fi
  
+ if test "$SASLFLAGS" != ""; then
+ 	V_INCLS="$V_INCLS $SASLFLAGS"
+ fi
  # Check whether --enable-largefile or --disable-largefile was given.
  if test "${enable_largefile+set}" = set; then
    enableval="$enable_largefile"