I am afraid to try a new version at the moment because the mail system is in production and I don't want to break it.
If I did upgrade to a newer version would the current configuration files be written over and would I have to do everything from scratch again?
On 4/9/2011 2:07 PM, Stephan Bosch wrote:
Op 8-4-2011 20:07, Jay Welch schreef:
Hi,
I am having compiling issues with Sieve and I am not sure what the error is stating.
[root@iosmail dovecot-sieve-1.0.4]# make make all-recursive make[1]: Entering directory
/home/jayw/Desktop/dovecot-sieve-1.0.4' Making all in src make[2]: Entering directory
/home/jayw/Desktop/dovecot-sieve-1.0.4/src' Making all in libsieve make[3]: Entering directory/home/jayw/Desktop/dovecot-sieve-1.0.4/src/libsieve' /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot/dovecot-1.0.7 -I/usr/src/dovecot/dovecot-1.0.7/src/lib -I../../src @CFLAGS@ -MT addr.lo -MD -MP -MF .deps/addr.Tpo -c -o addr.lo addr.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot/dovecot-1.0.7 -I/usr/src/dovecot/dovecot-1.0.7/src/lib -I../../src @CFLAGS@ -MT addr.lo -MD -MP -MF .deps/addr.Tpo -c addr.c -fPIC -DPIC -o .libs/addr.o gcc: @CFLAGS@: No such file or directory make[3]: *** [addr.lo] Error 1 make[3]: Leaving directory
/home/jayw/Desktop/dovecot-sieve-1.0.4/src/libsieve' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory/home/jayw/Desktop/dovecot-sieve-1.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory
/home/jayw/Desktop/dovecot-sieve-1.0.4' make: *** [all] Error 2Also, I did not originally have the source files and I had to download them for *dovecot-config*. Not sure if that makes a difference or not.
Why are you compiling these ancient relics? We're at Dovecot v2.0 these days. :)
Also, I don't see much to go on here. Apparently, @CFLAGS@ is not properly substituted, but I cannot tell you why.
My advice: try a (much) newer version.
Regards,
Stephan.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.