Sorry I've sent a config.log but get retained for approval.
This is the beginning of the file:
This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake.
It was created by Pigeonhole configure 0.3.3, which was generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-dovecot=/home/jc/rpmbuild/BUILD/dovecot-2.1.10 --with-managesieve=yes --enable-header-install=yes INSTALL_DATA=install -c -p -m644
---------
Platform.
---------
hostname = testv.fi.upm.es uname -m = x86_64 uname -r = 2.6.18-308.13.1.el5debug uname -s = Linux uname -v = #1 SMP Tue Aug 21 18:34:48 EDT 2012
/usr/bin/uname -p = unknown /bin/uname -X = unknown
/bin/arch = x86_64 /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown
Regards Juan C. Blanco
On 19/09/2012 20:07, Stephan Bosch wrote:
On 9/19/2012 6:22 PM, Juan C. Blanco wrote:
On 18/09/2012 20:49, Stephan Bosch wrote:
On 9/18/2012 8:18 PM, Juan C. Blanco wrote:
It seems that the error is related to the ld.gold fix, If I revert the c52a0c561311 patch the error is not produced
Oh d'oh. Yes, it related to that. I fixed it for Dovecot v2.2 before, but I forgot the Dovecot v2.1 tree. Fixed now:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/66adbdd89d5c
D'oh, this is the v2.2 change. The URL I meant is this one:
http://hg.rename-it.nl/dovecot-2.1-pigeonhole/rev/8144fb698cb3
This only happens when you compile against installed Dovecot headers, people using --with-dovecot= (like me) would not have seen this.
I'll push out a new release once 2.1.10 comes out. I'm being told that is imminent.
Sorry, but using the new 0.3.3 version I'm getting the same error and I'm also using --with-dovecot=... with the dovecot 2.1.10 tree in configure, not the installed headers. If needed I can send you the configure invocation command.
Yes, that could be helpful.
Regards,
Stephan.