Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
On 28/10/2010 20:49, Axel Thimm wrote:
On Thu, 2010-10-28 at 10:24 +0200, Juan C. Blanco wrote:
On 27/10/2010 20:16, Axel Thimm wrote:
On Mon, 2010-10-04 at 19:05 +0200, Juan C. Blanco wrote:
I've dounloaded the archive for pigeonhole, once decompressed:
If I do:
./configure --with-dovecot=../dovecot-2.0.5
make
All seems to work fine
But if I do (like the atrpms package spec):
autoreconf -ifv
./configure --with-dovecot=../dovecot-2.0.5
make
I get the error:
I checked the pigeonhole specfiles at ATrpms, but could not find any
such call, the %build part has been
%build
## crude hack ...
#./autogen.sh
%configure --with-dovecot=%{_libdir}/dovecot \
--with-managesieve=yes \
--enable-header-install=yes \
INSTALL_DATA=install -c -p -m644
make
for quite some time now.
Thans, I've seen so, but I have a question does not will be necessary to
do it?, the configure was generated by a version of autoconf newer than
the one in CentOS and dows not it may cause problems to use it as is.
It doesn't matter, autotools, the collection of autoconf, automake,
libtool and gettext are only needed when preparing the sources for
shipping, e.g. they are (normally) not needed for builds. Normally means
unless you change any configure.ac, Makefile.am, *.m4 files that these
tools need as an input for generating the build system files.
So you don't need to run autoreconf. But if you do need to run it (which
I also had to yesterday while chasing for a bug), you sometimes need to
nuke away some files, especially if your autotools are older that the
authors', so try
rm -f m4/lt* m4/libtool.m4 build-aux/ltmain.sh
autoreconf -fiv
./configure ...
And that should work on CentOS5. But as said, you don't need it. I added
the two lines above in the latest dovecot-pigeonhole rpm (commented) to
allow future users to easily enable rebuilding of the autotools bit.
OK, thanks for the the explanation I'm not a developer as yu can see :-)
Also note that there are fresh rpms for CentOS at ATrpms. :)
Yes, thanks a lot for keeping it
Regards
Jua C. Blanco
--
++
| Juan C. Blanco |
||
| Centro de Calculo | |
| Facultad de Informatica U.P.M. | E-mail: jcbla...@fi.upm.es |
| Campus de Montegancedo | |
| Boadilla del Monte | Tel.:(+34) 91 336 7466 |
| 28660 MADRID (Spain) | Fax :(+34) 91 336 6913 |
++
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
On 27/10/2010 20:16, Axel Thimm wrote:
Hi Juan,
Hi,
sorry for the late reply I just picked this up mentioning ATrpms:
On Mon, 2010-10-04 at 19:05 +0200, Juan C. Blanco wrote:
Hello Stephan I have some problems to build pigeonhole 0.2.1 over dovect
2.0.5, I've had no problems with previous versions; the system is CentOS
5.5.
FWIW CentOS is supported at ATrpms and there are packages for 0.2.1
there for CentOS, if you need them.
I think that is autotools related, but not sure.
I've dounloaded the archive for pigeonhole, once decompressed:
If I do:
./configure --with-dovecot=../dovecot-2.0.5
make
All seems to work fine
But if I do (like the atrpms package spec):
autoreconf -ifv
./configure --with-dovecot=../dovecot-2.0.5
make
I get the error:
I checked the pigeonhole specfiles at ATrpms, but could not find any
such call, the %build part has been
%build
## crude hack ...
#./autogen.sh
%configure --with-dovecot=%{_libdir}/dovecot \
--with-managesieve=yes \
--enable-header-install=yes \
INSTALL_DATA=install -c -p -m644
make
for quite some time now.
Thans, I've seen so, but I have a question does not will be necessary to
do it?, the configure was generated by a version of autoconf newer than
the one in CentOS and dows not it may cause problems to use it as is.
Regards
Juan C: blanco
--
++
| Juan C. Blanco |
||
| Centro de Calculo | |
| Facultad de Informatica U.P.M. | E-mail: jcbla...@fi.upm.es |
| Campus de Montegancedo | |
| Boadilla del Monte | Tel.:(+34) 91 336 7466 |
| 28660 MADRID (Spain) | Fax :(+34) 91 336 6913 |
++
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
On Thu, 2010-10-28 at 10:24 +0200, Juan C. Blanco wrote:
On 27/10/2010 20:16, Axel Thimm wrote:
On Mon, 2010-10-04 at 19:05 +0200, Juan C. Blanco wrote:
I've dounloaded the archive for pigeonhole, once decompressed:
If I do:
./configure --with-dovecot=../dovecot-2.0.5
make
All seems to work fine
But if I do (like the atrpms package spec):
autoreconf -ifv
./configure --with-dovecot=../dovecot-2.0.5
make
I get the error:
I checked the pigeonhole specfiles at ATrpms, but could not find any
such call, the %build part has been
%build
## crude hack ...
#./autogen.sh
%configure --with-dovecot=%{_libdir}/dovecot \
--with-managesieve=yes \
--enable-header-install=yes \
INSTALL_DATA=install -c -p -m644
make
for quite some time now.
Thans, I've seen so, but I have a question does not will be necessary to
do it?, the configure was generated by a version of autoconf newer than
the one in CentOS and dows not it may cause problems to use it as is.
It doesn't matter, autotools, the collection of autoconf, automake,
libtool and gettext are only needed when preparing the sources for
shipping, e.g. they are (normally) not needed for builds. Normally means
unless you change any configure.ac, Makefile.am, *.m4 files that these
tools need as an input for generating the build system files.
So you don't need to run autoreconf. But if you do need to run it (which
I also had to yesterday while chasing for a bug), you sometimes need to
nuke away some files, especially if your autotools are older that the
authors', so try
rm -f m4/lt* m4/libtool.m4 build-aux/ltmain.sh
autoreconf -fiv
./configure ...
And that should work on CentOS5. But as said, you don't need it. I added
the two lines above in the latest dovecot-pigeonhole rpm (commented) to
allow future users to easily enable rebuilding of the autotools bit.
Also note that there are fresh rpms for CentOS at ATrpms. :)
--
http://thimm.gr/ - http://ATrpms.net/
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
Hi Juan,
sorry for the late reply I just picked this up mentioning ATrpms:
On Mon, 2010-10-04 at 19:05 +0200, Juan C. Blanco wrote:
Hello Stephan I have some problems to build pigeonhole 0.2.1 over dovect
2.0.5, I've had no problems with previous versions; the system is CentOS
5.5.
FWIW CentOS is supported at ATrpms and there are packages for 0.2.1
there for CentOS, if you need them.
I think that is autotools related, but not sure.
I've dounloaded the archive for pigeonhole, once decompressed:
If I do:
./configure --with-dovecot=../dovecot-2.0.5
make
All seems to work fine
But if I do (like the atrpms package spec):
autoreconf -ifv
./configure --with-dovecot=../dovecot-2.0.5
make
I get the error:
I checked the pigeonhole specfiles at ATrpms, but could not find any
such call, the %build part has been
%build
## crude hack ...
#./autogen.sh
%configure --with-dovecot=%{_libdir}/dovecot \
--with-managesieve=yes \
--enable-header-install=yes \
INSTALL_DATA=install -c -p -m644
make
for quite some time now.
--
http://thimm.gr/ - http://ATrpms.net/
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
On 06/10/2010 21:34, Stephan Bosch wrote: Op 4-10-2010 19:05, Juan C. Blanco schreef: Hello Stephan I have some problems to build pigeonhole 0.2.1 over dovect 2.0.5, I've had no problems with previous versions; the system is CentOS 5.5. I think that is autotools related, but not sure. I've dounloaded the archive for pigeonhole, once decompressed: If I do: ./configure --with-dovecot=../dovecot-2.0.5 make All seems to work fine But if I do (like the atrpms package spec): autoreconf -ifv ./configure --with-dovecot=../dovecot-2.0.5 make I get the error: Hope you can give me some light abaout this Not much, unfortunately. I can't make much sense of the error messages. For some reason it interprets the individual elements of some compile command as shell commands. Looks like your autotools/libtool installation is broken or maybe there's a version mismatch. Maybe but all the tools are the original from CentOS 5.5, all builds for previous versions of pigeonhole have worked fine. With the same base system and dovecot version I can build the previous version of pigeonhole (0.2.0) without problems, in this case the configure does not work without a previous autoreconf. With the 0.2.1 version only builds without the autoreconf I'll look more on the issue. Best regards Juan C. Blanco Regards, Stephan -- ++ | Juan C. Blanco | || | Centro de Calculo | | | Facultad de Informatica U.P.M. | E-mail: jcbla...@fi.upm.es | | Campus de Montegancedo | | | Boadilla del Monte | Tel.:(+34) 91 336 7466 | | 28660 MADRID (Spain) | Fax :(+34) 91 336 6913 | ++
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
On 08/10/2010 11:45, Juan C. Blanco wrote: On 06/10/2010 21:34, Stephan Bosch wrote: Op 4-10-2010 19:05, Juan C. Blanco schreef: Hello Stephan I have some problems to build pigeonhole 0.2.1 over dovect 2.0.5, I've had no problems with previous versions; the system is CentOS 5.5. I think that is autotools related, but not sure. I've dounloaded the archive for pigeonhole, once decompressed: If I do: ./configure --with-dovecot=../dovecot-2.0.5 make All seems to work fine But if I do (like the atrpms package spec): autoreconf -ifv ./configure --with-dovecot=../dovecot-2.0.5 make I get the error: Hope you can give me some light abaout this Not much, unfortunately. I can't make much sense of the error messages. For some reason it interprets the individual elements of some compile command as shell commands. Looks like your autotools/libtool installation is broken or maybe there's a version mismatch. Maybe but all the tools are the original from CentOS 5.5, all builds for previous versions of pigeonhole have worked fine. With the same base system and dovecot version I can build the previous version of pigeonhole (0.2.0) without problems, in this case the configure does not work without a previous autoreconf. With the 0.2.1 version only builds without the autoreconf I'll look more on the issue. Well I have some idea about the problem, the $echo macro used in libtool is emty with 0.2.1 and has the value echo in 0.2.0, I don't know th reason for this. However if I make a clone of the HG sources and then execute autgen.sh the build works fine after that. Regards Juan C. Blanco Best regards Juan C. Blanco Regards, Stephan
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
Op 4-10-2010 19:05, Juan C. Blanco schreef: Hello Stephan I have some problems to build pigeonhole 0.2.1 over dovect 2.0.5, I've had no problems with previous versions; the system is CentOS 5.5. I think that is autotools related, but not sure. I've dounloaded the archive for pigeonhole, once decompressed: If I do: ./configure --with-dovecot=../dovecot-2.0.5 make All seems to work fine But if I do (like the atrpms package spec): autoreconf -ifv ./configure --with-dovecot=../dovecot-2.0.5 make I get the error: Hope you can give me some light abaout this Not much, unfortunately. I can't make much sense of the error messages. For some reason it interprets the individual elements of some compile command as shell commands. Looks like your autotools/libtool installation is broken or maybe there's a version mismatch. Regards, Stephan
Re: [Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
Hello Stephan I have some problems to build pigeonhole 0.2.1 over dovect 2.0.5, I've had no problems with previous versions; the system is CentOS 5.5. I think that is autotools related, but not sure. I've dounloaded the archive for pigeonhole, once decompressed: If I do: ./configure --with-dovecot=../dovecot-2.0.5 make All seems to work fine But if I do (like the atrpms package spec): autoreconf -ifv ./configure --with-dovecot=../dovecot-2.0.5 make I get the error: make all-recursive make[1]: Entering directory `/home/jc/dovecot-2.0-pigeonhole-0.2.1' Making all in src make[2]: Entering directory `/home/jc/dovecot-2.0-pigeonhole-0.2.1/src' Making all in lib-sieve make[3]: Entering directory `/home/jc/dovecot-2.0-pigeonhole-0.2.1/src/lib-sieve' Making all in plugins make[4]: Entering directory `/home/jc/dovecot-2.0-pigeonhole-0.2.1/src/lib-sieve/plugins' Making all in vacation make[5]: Entering directory `/home/jc/dovecot-2.0-pigeonhole-0.2.1/src/lib-sieve/plugins/vacation' if /bin/sh ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../.. -I./../../ -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5 -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-dict -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-mail -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-imap -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-charset -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-index -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-storage -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-storage/index -I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-storage/index/raw -std=gnu99 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -MT cmd-vacation.lo -MD -MP -MF .deps/cmd-vacation.Tpo -c -o cmd-vacation.lo cmd-vacation.c; \ then mv -f .deps/cmd-vacation.Tpo .deps/cmd-vacation.Plo; else rm -f .deps/cmd-vacation.Tpo; exit 1; fi ../../../../libtool: line 813: X--tag=CC: command not found ../../../../libtool: line 846: libtool: ignoring unknown tag : command not found ../../../../libtool: line 813: X--mode=compile: command not found ../../../../libtool: line 979: *** Warning: inferring the mode of operation is deprecated.: command not found ../../../../libtool: line 980: *** Future versions of Libtool will require --mode=MODE be specified.: command not found ../../../../libtool: line 1123: Xgcc: command not found ../../../../libtool: line 1123: X-DHAVE_CONFIG_H: command not found ../../../../libtool: line 1123: X-I.: command not found ../../../../libtool: line 1123: X-I.: command not found ../../../../libtool: line 1123: X-I../../../..: No such file or directory ../../../../libtool: line 1123: X-I../../../..: No such file or directory ../../../../libtool: line 1123: X-I./../../: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-dict: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-mail: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-imap: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-charset: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-index: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-storage: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-storage/index: No such file or directory ../../../../libtool: line 1123: X-I/home/jc/rpmbuild/BUILD/dovecot-2.0.5/src/lib-storage/index/raw: No such file or directory ../../../../libtool: line 1123: X-std=gnu99: command not found ../../../../libtool: line 1123: X-O2: command not found ../../../../libtool: line 1123: X-g: command not found ../../../../libtool: line 1123: X-pipe: command not found ../../../../libtool: line 1123: X-Wall: command not found ../../../../libtool: line 1123: X-Wp,-D_FORTIFY_SOURCE=2: command not found ../../../../libtool: line 1123: X-fexceptions: command not found ../../../../libtool: line 1123: X-fstack-protector: command not found ../../../../libtool: line 1123: X--param=ssp-buffer-size=4: command not found ../../../../libtool: line 1123: X-m64: command not found ../../../../libtool: line 1123: X-mtune=generic: command not found ../../../../libtool: line 1123: X-Wall: command not found
[Dovecot] Released Pigeonhole v0.2.1 for Dovecot v2.0.4
Hello Dovecot users, There haven't been that many Pigeonhole developments lately, not even really significant bugs were reported. That is why this release is pretty small in terms of changes. However, one issue got some attention: the fact that not recompiling Pigeonhole for Dovecot v2.0.3 would result in rather interesting message delivery. Normally, Dovecot would complain about a version mismatch, but unfortunately Pigeonhole's Sieve plugin didn't record the Dovecot version it was compiled with. Starting with this release, such problems should not occur again. Changelog v0.2.1: + Incorporated distinction between original and final envelope recipient in Sieve interpreter, as recently introduced in Dovecot. + Regex extension: added support for regex keys composed from variables. - LDA Sieve plugin: added _version symbol to enable Dovecot's plugin version check. Without this check, people can forget to recompile the plugin, which can lead to unexpected effects. - LDA Sieve plugin: turned debug message about an unconfigured home directory into a proper error and added script path information. - Fixed unnecessary reporting of dummy extensions in ManageSieve SIEVE capability; the comparator-i;octet and comparator-i;ascii-numeric 'extensions' were reported explicitly. The release is available as follows: http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.1.tar.gz http://www.rename-it.nl/dovecot/2.0/dovecot-2.0-pigeonhole-0.2.1.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.0 wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch step...@rename-it.nl
