Fred Moyer and Michael Peters were correct about not wanting to
have 5.8.x libraries under perl 5.10.1. As soon as I built a
5.10.1 cleanly with no retained libraries, the undef's in
Dynaload in mod_perl2 make test went away.
The biggest remaining problem was getting apreq2-2.12 to build
Hi Fred,
Decided to look at the source found by your 'ack'.
It turns out that, in file pad.c, someone in the perl 5.10.0 or 5.10.1
project decided that the Perl_pad_sv routine was only needed if
-DDEBUGGING was specified for the Perl build.
Fixed this by commenting out the #ifdef DEBUGGING at
cr...@animalhead.com wrote:
I have always included previous perl libraries in the @INC of
new builds. And it has always worked, with the single
exception of building mod_perl2 this time. All of the perl
scripts and modules on my site work well under the new 5.10.1.
Pure Perl modules should
On Sep 2, 2009, at 6:21 AM, Michael Peters wrote:
cr...@animalhead.com wrote:
I have always included previous perl libraries in the @INC of
new builds. And it has always worked, with the single
exception of building mod_perl2 this time. All of the perl
scripts and modules on my site work
A bit more data on the problem reported below:
/build/modperl-2.0 $ grep -r Perl_pad_sv *
Binary file src/modules/perl/mod_perl.so matches
/build/modperl-2.0 $ ll src/modules/perl/mod_perl.so
-rwxr-xr-x 1 user wheel 1559168 Aug 29 21:22 src/modules/perl/
mod_perl.so
/build/modperl-2.0 $ cd
On Tue, Sep 1, 2009 at 9:27 AM, cr...@animalhead.com wrote:
A bit more data on the problem reported below:
/build/modperl-2.0 $ grep -r Perl_pad_sv *
Binary file src/modules/perl/mod_perl.so matches
/build/modperl-2.0 $ ll src/modules/perl/mod_perl.so
-rwxr-xr-x 1 user wheel 1559168 Aug
Can you please cc the list on all replies?
On Tue, Sep 1, 2009 at 5:41 PM, cr...@animalhead.com wrote:
cd /build/perl-5.10.1/
make veryclean
./Configure -Dd_dosuid
[cc'ing the list as to not break the thread]
On Tue, Sep 1, 2009 at 7:41 PM, cr...@animalhead.com wrote:
I have always included previous perl libraries in the @INC of
new builds. And it has always worked, with the single
exception of building mod_perl2 this time. All of the perl
scripts and
But this is the mod_perl mailing list. It is the place to which
one sends reports of bugs or problems with mod_perl. I sent such
a report, citing this undefined symbol when building mod_perl2.
It is hard for me to imagine that the fact that I gave the perl
build process a list of directories
On Tue, Sep 1, 2009 at 10:14 PM, cr...@animalhead.com wrote:
But this is the mod_perl mailing list. It is the place to which
one sends reports of bugs or problems with mod_perl. I sent such
a report, citing this undefined symbol when building mod_perl2.
Right, but if you are mixing major
On Sat, Aug 29, 2009 at 9:43 PM, cr...@animalhead.com wrote:
-8-- Start Bug Report 8--
1. Problem Description:
I have upgraded to Apache 2.2.13 and Perl 5.10.1. Both seem to be working
OK,
although Apache with using my old mod_perl 2.04 that uses perl
-8-- Start Bug Report 8--
1. Problem Description:
I have upgraded to Apache 2.2.13 and Perl 5.10.1. Both seem to be
working OK,
although Apache with using my old mod_perl 2.04 that uses perl 5.8.9.
make test in both the release mod_perl 2.0.4 and the
12 matches
Mail list logo
