[Dovecot] CVS/test version config/build failures on FreeBSD
While diagnosing a problem I was having with IMAP and SSL (which I ended up fixing by simply upgrading from 0.99.9.1 to 0.99.10, and possibly affected by upgrading openssl libs from 0.9.7a to 0.9.7.b), I attempted to try the CVS version of Dovecot.
When using the CVS version, apparently I have to first generate 'configure' using autogen.sh (?). This was the result of that, on FreeBSD 4.8-STABLE (2003-08-06):
# ./autogen.sh
automake: configure.in: installing ./install-sh' automake: configure.in: installing ./mkinstalldirs'
automake: configure.in: installing ./missing' configure.in: 3: required file ./config.h.in' not found
automake: configure.in: installing ./depcomp' configure.in:3: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:13: warning: AC_ARG_PROGRAM invoked multiple times configure.in:1126: warning: do not use m4_regexp: use regexp or m4_bregexp autoheader: config.h.in' is created
And then...
# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc
checking for strerror in -lcposix... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking dependency style of gcc... (cached) gcc
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for gcc option to accept ANSI C... none needed
checking for inline... inline
checking build system type... i386-unknown-freebsdelf4.8
checking host system type... i386-unknown-freebsdelf4.8
checking for ranlib... ranlib
checking for ld used by GCC... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
loading cache /dev/null within ltconfig
./ltconfig: .: /dev/null: not a regular file
ltconfig: you must specify a host type if you use --no-verify' Try ltconfig --help' for more information.
configure: error: libtool configure failed
I also attempted to use 0.99.11-test4 from http://dovecot.procontrol.fi/test/, but this failed to build:
[...] Making all in maildir gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-index/maildir -I../../../../src/lib-storage -I../../../../src/lib-storage/index -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c maildir-copy.c make: don't know how to make ../../../../src/lib-storage/index/index-expunge.h. Stop *** Error code 1
Stop in /usr/local/src/dovecot/dovecot-0.99.11-test4/src/lib-storage/index.
Just thought you'd like to know :)
-Mike
On Saturday 09 August 2003 10:42 pm, Mike Brown wrote:
While diagnosing a problem I was having with IMAP and SSL (which I ended up fixing by simply upgrading from 0.99.9.1 to 0.99.10, and possibly affected by upgrading openssl libs from 0.9.7a to 0.9.7.b), I attempted to try the CVS version of Dovecot.
When using the CVS version, apparently I have to first generate 'configure' using autogen.sh (?). This was the result of that, on FreeBSD 4.8-STABLE (2003-08-06):
# ./autogen.sh automake: configure.in: installing
./install-sh' automake: configure.in: installing./mkinstalldirs' automake: configure.in: installing./missing' configure.in: 3: required file./config.h.in' not found automake: configure.in: installing./depcomp' configure.in:3: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:13: warning: AC_ARG_PROGRAM invoked multiple times configure.in:1126: warning: do not use m4_regexp: use regexp or m4_bregexp autoheader:config.h.in' is created
As far as I know these are harmless.
And then...
# ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets ${MAKE}... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking dependency style of gcc... gcc checking for strerror in -lcposix... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking dependency style of gcc... (cached) gcc checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for gcc option to accept ANSI C... none needed checking for inline... inline checking build system type... i386-unknown-freebsdelf4.8 checking host system type... i386-unknown-freebsdelf4.8 checking for ranlib... ranlib checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes loading cache /dev/null within ltconfig ./ltconfig: .: /dev/null: not a regular file ltconfig: you must specify a host type if you use
--no-verify' Tryltconfig --help' for more information. configure: error: libtool configure failed
You might want to duplicate most of the configure arguments from the port.
I also attempted to use 0.99.11-test4 from http://dovecot.procontrol.fi/test/, but this failed to build:
[...] Making all in maildir gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../../src/lib
-I../../../../src/lib-mail -I../../../../src/lib-imap
-I../../../../src/lib-index -I../../../../src/lib-index/maildir -I../../../../src/lib-storage -I../../../../src/lib-storage/index -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c maildir-copy.c make: don't know how to make ../../../../src/lib-storage/index/index-expunge.h. Stop *** Error code 1
Timo fixed this in CVS :-)
Stop in /usr/local/src/dovecot/dovecot-0.99.11-test4/src/lib-storage/index.
Just thought you'd like to know :)
-Mike
Thanks,
Dominic <dom at wirespeed.org.uk>
Dominic Marks wrote:
On Saturday 09 August 2003 10:42 pm, Mike Brown wrote:
./ltconfig: .: /dev/null: not a regular file ltconfig: you must specify a host type if you use
--no-verify' Tryltconfig --help' for more information. configure: error: libtool configure failedYou might want to duplicate most of the configure arguments from the port.
Ah, I see you're the port maintainer.
Adding arguments didn't make a difference...
./configure --localstatedir=/var --with-ssl=openssl
--with-ssldir=/var/dovecot/ssl --with-pop3d --with-pam
CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib
I infer that you have no trouble with the latest CVS version?
On Sunday 10 August 2003 3:23 pm, Mike Brown wrote:
Dominic Marks wrote:
On Saturday 09 August 2003 10:42 pm, Mike Brown wrote:
./ltconfig: .: /dev/null: not a regular file ltconfig: you must specify a host type if you use
--no-verify' Tryltconfig --help' for more information. configure: error: libtool configure failedYou might want to duplicate most of the configure arguments from the port.
Ah, I see you're the port maintainer.
Yep.
Adding arguments didn't make a difference...
./configure --localstatedir=/var --with-ssl=openssl
--with-ssldir=/var/dovecot/ssl --with-pop3d --with-pam
CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/libI infer that you have no trouble with the latest CVS version?
I keep a development copy of the port tracking the test releases and I have test4 building fine here. I had to add a hack to get the index-expunge.h file copied, but Timo has fixed that now.
As someone else said, and I suspected, you probably need to update libtool. I'm using libtool 1.3.5_1 from ports.
On an unrelated note do you have some abstract email configurations ? I hit Reply-All in KMail to your message and added your address to the To: and Cc: lines, but didn't include the mailing list. Alternatively it could be my email configurations :) or just KMail being odd.
On an even more unrelated note: Timo: any chance of the kqueue ioloop patch I submitted to you being integrated ? I'm willing to have a go at removing the priorities stuff in ioloop and ioloop_{poll,select} if that would help.
Cheers,
Dominic <dom at wirespeed.org.uk>
On Sunday, Aug 10, 2003, at 22:07 Europe/Helsinki, Dominic Marks wrote:
On an even more unrelated note: Timo: any chance of the kqueue ioloop patch I submitted to you being integrated ? I'm willing to have a go at removing the priorities stuff in ioloop and ioloop_{poll,select} if that would help.
Well, it's in TODO .. :) I did actually remove the priority stuff from ioloop, so if you'll just update the patch I'll commit it to CVS.
On Sunday 10 August 2003 6:56 pm, Timo Sirainen wrote:
On Sunday, Aug 10, 2003, at 22:07 Europe/Helsinki, Dominic Marks wrote:
On an even more unrelated note: Timo: any chance of the kqueue ioloop patch I submitted to you being integrated ? I'm willing to have a go at removing the priorities stuff in ioloop and ioloop_{poll,select} if that would help.
Well, it's in TODO .. :) I did actually remove the priority stuff from ioloop, so if you'll just update the patch I'll commit it to CVS.
Should have it ready for review in a short time then :-)
Thanks,
Dominic <dom at wirespeed.org.uk>
Dominic Marks wrote:
As someone else said, and I suspected, you probably need to update libtool. I'm using libtool 1.3.5_1 from ports.
I was using 1.3.4 from the ports. I upgraded, but it did not help. Oh well, I'm not going to worry about it, since the dovecot port works for me.
On an unrelated note do you have some abstract email configurations ? I hit Reply-All in KMail to your message and added your address to the To: and Cc: lines, but didn't include the mailing list.
My message came through the list with two Cc lines: one for me and one for the list (your address was in the To). I think it was rewritten at procontrol.fi, because it went out of my system with a single CC line.
On Monday, Aug 11, 2003, at 01:26 Europe/Helsinki, Mike Brown wrote:
My message came through the list with two Cc lines: one for me and one for the list (your address was in the To). I think it was rewritten at procontrol.fi, because it went out of my system with a single CC line.
Hmm. That's strange. Lets see if it happens with this message too..
On Sun, 2003-08-10 at 01:42, Mike Brown wrote:
When using the CVS version,
That's really not a good idea at the moment. The indexing code is still pretty broken there.
apparently I have to first generate 'configure' using autogen.sh (?).
Yes.
loading cache /dev/null within ltconfig ./ltconfig: .: /dev/null: not a regular file ltconfig: you must specify a host type if you use
--no-verify' Tryltconfig --help' for more information. configure: error: libtool configure failed
Looks like some automake/libtool incompatibility. You'll probably have to upgrade libtool.
participants (3)
-
Dominic Marks
-
Mike Brown
-
Timo Sirainen