Package: log4cpp
Version: 1.0-2
Severity: serious

Dear maintainer of log4cpp,

your latest revision introduced a patch to configure{,.in}.  This
updates the timestamp of both files and, lacking maintainer mode,
causes the Autotools scripts to rerun automake and autoconf
which subsequently fails.  The package does not depend on those tools
and not all necessary m4 defines needed to reproduce the build system
are provided in the tarball.

Your package failed to auto-build on sparc because of this issue but
I could easily reproduce the issue on my machine by calling
`debian/rules apply-patches' and then running `./configure && make'.

[...]
config.status: creating include/config.h
config.status: executing depfiles commands
creating include/log4cpp/config.h - prefix LOG4CPP for include/config.h defines
dirname: extra operand `/boot'
Try `dirname --help' for more information.
/* automatically generated bcb5/ config/ debian/ doc/ include/ m4/ msvc6/ 
openvms/ patches/ src
/usr/bin/make -C . 
make[1]: Entering directory `/build/buildd/log4cpp-1.0'
cd . && /bin/sh /build/buildd/log4cpp-1.0/config/missing --run aclocal-1.10 
/usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of 
AM_PATH_LIBMCRYPT
/usr/share/aclocal/libmcrypt.m4:17:   run info '(automake)Extending aclocal'
/usr/share/aclocal/libmcrypt.m4:17:   or see 
http://sources.redhat.com/automake/automake.html#Extending-aclocal
 cd . && /bin/sh /build/buildd/log4cpp-1.0/config/missing --run automake-1.10 
--gnu 
Makefile.am:1: DOC does not appear in AM_CONDITIONAL
make[1]: *** [Makefile.in] Error 1
make[1]: Leaving directory `/build/buildd/log4cpp-1.0'
make: *** [debian/stamp-makefile-build] Error 2
******************************************************************************
Build finished at 20071027-0440
FAILED [dpkg-buildpackage died]
Purging chroot-unstable/build/buildd/log4cpp-1.0

Kind regards,
Philipp Kern
Debian Developer



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to