[Dovecot] Error Building v2.2

Christian Wiese christian.wiese at securepoint.de
Tue Mar 26 16:42:35 EET 2013

Hi Nick,

> Tried with dovecot-2-2-pigeonhole-097764f6bbe3 which I renamed as 
> dovecot-2.2-pigeonhole-0.3.4 and at some point it failed as well:
> ...
> + pushd dovecot-2.2-pigeonhole-0.3.4
> ~/rpmbuild/BUILD/dovecot-2.2.0/dovecot-2.2-pigeonhole-0.3.4 
> ~/rpmbuild/BUILD/dovecot-2.2.0
> + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic 
> -fno-strict-aliasing'
> + export CFLAGS
> + CXXFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic'
> + export CXXFLAGS
> + FFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic 
> -I/usr/lib64/gfortran/modules'
> + export FFLAGS
> + ./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=/var/lib --mandir=/usr/share/man
> --infodir=/usr/share/info 'INSTALL_DATA=install -c -p -m644'
> --disable-static --with-dovecot=../
> --without-unfinished-features /var/tmp/rpm-tmp.yRHSSw: line
> 93: ./configure: No such file or directory error: Bad exit status
> from /var/tmp/rpm-tmp.yRHSSw (%build)
> Any ideas?

Without knowing the spec file it is hard to tell but I think that you
didn't run autogen.sh shipped with the dovecot-pigeonhole sources,
because "./configure: No such file or directory error" is kind of
explicit about what went wrong.
So I bet you simply need to run the 'autogen.sh' script shipped with
the pigeonhole sources, to get a configure script generated.
Needless to say that this has to be done before actually calling
configure, so most probably calling autogen.sh right after the "pushd
dovecot-2.2-pigeonhole-0.3.4" might be a good idea ;)


More information about the dovecot mailing list