Bug#468327: libapache2-mod-perl2: FTBFS on sparc: oh darn, server dumped core

[Niko Tyni]

Package: libapache2-mod-perl2
Version: 2.0.3-3
Severity: serious

This package failed to build on sparc. From the buildd log:

ulimit -c unlimited; /usr/bin/perl /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/TEST -bugreport -verbose=0
/usr/sbin/apache2  -d /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t -f /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/conf/httpd.conf -D APACHE2 -D PERL_USEITHREADS
using Apache/2.2.8 (worker MPM)

waiting 180 seconds for server to start: .[  error] 
server has died with status 255 (please examine t/logs/error_log)
[  error] oh darn, server dumped core 
[  error] for stacktrace, run: gdb /usr/sbin/apache2 -core /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/core
sh: line 1: 17602 Terminated              /usr/bin/perl /build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry/t/TEST -bugreport -verbose=0
make[2]: *** [run_tests] Error 143
make[2]: Leaving directory `/build/buildd/libapache2-mod-perl2-2.0.3/ModPerl-Registry'
make[1]: *** [run_tests] Error 2
make[1]: Leaving directory `/build/buildd/libapache2-mod-perl2-2.0.3'
make: *** [build-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

Other architectures seem to be OK, at least those that are built so far.

As 2.0.3-2 built fine, this is possibly/probably a problem with the
Perl 5.10 patches introduced in -3 that were cherry-picked from the
upstream SVN.

Maybe we should upgrade to a full current upstream SVN snapshot first...

Cheers,
-- 
Niko Tyni   ntyni at debian.org