ScienceMan wrote:
Was this ever resolved? I have tried the flags suggested, but still see upon
doing a "make test" the following errors: (Have substituted [...] for my
work directory path
Couple of questions:
1) Are you using the system perl or did you build your own?
2) Are you using the sy
Was this ever resolved? I have tried the flags suggested, but still see upon
doing a "make test" the following errors: (Have substituted [...] for my
work directory path
cd t; make test
perl -MTest::Harness -e 'runtests(@ARGV)' version.t cookie.t params.t
parsers.t error.t util.t
versiondyl
Actually, I'm still using the default Apache2.. I did built mod_perl2 from
scratch. One of my fellow perl mongers installed Leopard before I did and
mentioned that he couldn't find mod_perl2 on it.. I just assumed that it
wasn't there so I rebuilt :)
Any ideas about the architecture signature in t
On Nov 10, 2007, at 8:00 PM, Hendrik Van Belleghem wrote:
To be honest, I haven't been able to get DBD::mysql compiled, nor
Apache2::Request (properly - still some strange errors in the
apache2 error log when I try to load it).
I haven't fully tested the Apache2 (or mod_perl for that matter).
Hi,
To be honest, I haven't been able to get DBD::mysql compiled, nor
Apache2::Request (properly - still some strange errors in the apache2 error
log when I try to load it).
I haven't fully tested the Apache2 (or mod_perl for that matter). I'm not
building it with PHP but it does appear to come wi
Slightly off-topic:
The 10.2 10.3 and maybe 10.4 versions of Apache that came with OS X
had library conflicts with mysql/php if you tried to compile modperl
1 or 2
Can I interpret your post to mean that one does not have to rebuild
Apache2 now too?
On Nov 10, 2007, at 9:56 AM, Hen
