[Kolab-devel] [issue1980] Kolab server HEAD: compile error with kolabd

Thomas Arendsen Hein kolab-issues at intevation.de
Thu Sep 13 11:42:56 CEST 2007


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

After ~180 minutes cvs-kolab.sh -i -F -H aborts with:

cp -p /kolabdevel/RPM/PKG/kolabconf-2.1.0.cvs-20070913.src.rpm .
cp kolabconf-2.1.0.cvs-20070913.src.rpm ../stage/
make[1]: Leaving directory `/kolabdevel/CVS/server/kolabconf'
make[1]: Entering directory `/kolabdevel/CVS/server/kolabd'
test -d /kolabdevel/RPM/SRC/kolabd || mkdir /kolabdevel/RPM/SRC/kolabd
cd kolabd && ./bootstrap && ./configure --prefix=/kolab --enable-dist=kolab \
                && make clean distcheck && mv kolabd-`grep 'm4_define(_VERSION'
/kolabdevel/CVS/server/kolabd/kolabd/configure.ac|sed
's/m4_define(_VERSION,\(.*\))/\1/'`.tar.bz2 /kolabdevel/RPM/SRC/kolabd
./bootstrap: line 2: autoreconf: command not found
make[1]: *** [all] Error 127
make[1]: Leaving directory `/kolabdevel/CVS/server/kolabd'
make: *** [kolab] Error 2
Not installing! Looks like the Kolab developers broke CVS. Bug them at
https://www.intevation.de/roundup/kolab


autoreconf is accessible if running as the kolabdevel user instead of root.
(with Kolab 2.2 all calls to openpkg, even installing RPM packages, can be done
as the management user, i.e. "kolabdevel" in this instance, so using the root
account can be avoided for many things.

----------
assignedto: wrobel
messages: 11901
nosy: thomas, wilde, wrobel
priority: urgent
status: unread
title: Kolab server HEAD: compile error with kolabd
topic: server
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue1980>
________________________________________________




More information about the devel mailing list