Hi Folks

Debian: 2.6.24-1-686
gcc: 4.2.3
Perl: 5.10.0
Apache: 2.2.8
mod_perl: 2.0.4

Debian upgraded Perl to 5.10.0 today, so I tried upgrading mod_perl to
2.0.4. This is the end of 'make test':
<===8<>===>
make[1]: Leaving directory `/home/ron/mod_perl-2.0.4/xs'
/usr/bin/perl -Iblib/arch -Iblib/lib \
        t/TEST -clean
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/ron/mod_perl-2.0.4/t/TEST
-clean
APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT=
APACHE_TEST_USER= APACHE_TEST_APXS= \
        /usr/bin/perl -Iblib/arch -Iblib/lib \
        t/TEST -bugreport -verbose=0 
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/ron/mod_perl-2.0.4/t/TEST
-bugreport -verbose=0
/home/ron/httpd/prefork/bin/httpd  -d /home/ron/mod_perl-2.0.4/t
-f /home/ron/mod_perl-2.0.4/t/conf/httpd.conf -D APACHE2 -D
PERL_USEITHREADS
using Apache/2.2.8 (prefork MPM)

waiting 120 seconds for server to start: .httpd: Syntax error on line 33
of /home/ron/mod_perl-2.0.4/t/conf/httpd.conf: Cannot
load /home/ron/mod_perl-2.0.4/src/modules/perl/mod_perl.so into
server: /home/ron/mod_perl-2.0.4/src/modules/perl/mod_perl.so: undefined
symbol: boot_DynaLoader
[  error] 
server has died with status 255 (t/logs/error_log wasn't created, start
the server in the debug mode)
sh: line 1:  6612
Terminated              /usr/bin/perl /home/ron/mod_perl-2.0.4/t/TEST
-bugreport -verbose=0
make: *** [run_tests] Error 143
<===8><===>

On my laptop I just ignored the error, ran 'sudo make install', and
restarted Apache. It worked.

On my desktop, same software, restarting Apache gives:
<===8><===>
[EMAIL PROTECTED]:~/mod_perl-2.0.4$ ~/httpd/prefork/bin/apachectl start
httpd: Syntax error on line 9
of /home/ron/httpd/prefork/conf/httpd.conf: Cannot
load /home/ron/httpd/prefork/modules/mod_perl.so into
server: /home/ron/httpd/prefork/modules/mod_perl.so: undefined symbol:
boot_DynaLoader
<===8><===>

I did not find any reference to this in the mail archives, although
Googling did give, for a non-Apache context, a suggestion it was due to
the order of parameters in the gcc command line. Hence the gcc version
number above.

Any ideas?

-- 
Ron Savage
[EMAIL PROTECTED]
http://savage.net.au/index.html


Reply via email to