Howdy all,
I've been trying to get installsieve to compile and install since v2.0.7.
In 2.0.8 and 2.0.9, it's Makefile is not even configured through the
configure script. I modified the configure script to build the Makefile in
order to try to use installsieve, but when I tried to compile, I got
several errors and it bombed. I'm not a programmer, so I'm a bit lost.
Everything else is set up and working great, btw. I've been really happy
with Cyrus as my imap server, but now I'd like to get support for
installing sieve scripts without having to manually add the files to the
directory structure.
The errors I get on compiling are as follows:
gcc -c -I. -I. -I./../lib -I./../acap -I/usr/local/db/include
-I/usr/local/include -I/usr/local/ssl/include -I/usr/lib/include
-I/usr/lib/include -DHAVE_CONFIG_H -I. -I. -g -O2 \
installscript.c
installscript.c:76: conflicting types for `STAT_CONT'
isieve.h:57: previous declaration of `STAT_CONT'
installscript.c:77: conflicting types for `STAT_NO'
isieve.h:58: previous declaration of `STAT_NO'
installscript.c:79: conflicting types for `STAT_OK'
isieve.h:60: previous declaration of `STAT_OK'
installscript.c:79: redefinition of `imt_stat'
isieve.h:60: `imt_stat' previously declared here
installscript.c: In function `simple':
installscript.c:156: warning: assignment makes pointer from integer without
a cast
installscript.c:157: warning: passing arg 1 of `fgets' discards `const'
from pointer target type
installscript.c:159: warning: assignment of read-only location
installscript.c: At top level:
installscript.c:285: conflicting types for `init_sasl'
isieve.h:52: previous declaration of `init_sasl'
installscript.c:373: conflicting types for `auth_sasl'
isieve.h:62: previous declaration of `auth_sasl'
installscript.c:463: conflicting types for `init_net'
isieve.h:47: previous declaration of `init_net'
installscript.c:490: conflicting types for `read_capability'
isieve.h:54: previous declaration of `read_capability'
make: *** [installscript.o] Error 1
Does anyone have any insight as to what's wrong?
Thanks,
Will Hardeman
[EMAIL PROTECTED]