Hello,
I sent a message a little while ago, when I couldn't `configure' Cyrus
due to a sasl_checkapop issue in the configure script. Rob Siemborski
pointed out what the problem was, and he fixed it in CVS. Rather than
grabbing the CVS, I fixed it in the configure script manually and tried
compiling.
`configure' worked, and I ran `make' - this is part of the error I
received (on FreeBSD 4.5, BDB 3.2, Cyrus SASL 2.1.2):
<SNIP>
### Making all in /u/devel/install/cyrus/cyrus-imapd-2.1.3/sieve
gcc -c -I. -I.. -I. -I./../lib -I/usr/local/BerkeleyDB.3.2/include
-I/usr/local/include -I/usr/local/cyrus-sasl/include -DHAVE_CONFIG_H -I.
-I. -Wall -g -O2 sieve.c
In file included from ../config.h:259,
from ./sieve.y:30:
/usr/include/sys/socket.h:52: syntax error before `sa_family_t'
/usr/include/sys/socket.h:52: warning: data definition has no type or
storage class
/usr/include/sys/socket.h:163: syntax error before `u_char'
/usr/include/sys/socket.h:174: syntax error before `u_short'
/usr/include/sys/socket.h:188: syntax error before `u_char'
/usr/include/sys/socket.h:190: `int64_t' undeclared here (not in a
function)
</SNIP>
So, rather than modifying anything else (I'm confident it was missing
the `sys/types.h' header - req'd by the FreeBSD sockets implementation)
I decided to grab the CVS instead.
When I retrieved the CVS for the Cyrus-IMAP head and ran `sh
./SMakefile.sh' followed by my configure statement, I get this in my
output from `configure':
checking for db_create in -ldb-3.3... no
checking for db_create in -ldb3.3... no
checking for db_create in -ldb-3.2... yes
checking "duplicate db" database backend... db3_nosync
checking "mboxlist" database backend... db3
checking "seen state" database backend... flat
checking "subscription" database backend... flat
checking "TLS cache" database backend... db3_nosync
./configure: line 4990: syntax error near unexpected token `yes:no'
./configure: line 4990: ` yes:no'
I've got M4 v1.4, autoconf v2.53, and automake/aclocal v1.6 installed.
There were some simple warnings, but no errors reported when running the
SMakefile script. Perhaps I did something wrong when I checked out the
CVS, and generated the configure script?
As things are right now, I'm going to work with the released v2.1.3, and
add the appropriate header to get past the socket.h errors - perhaps
someone can patch this in CVS?
Thanks,
-David Fuchs
