On Wednesday 28 April 2004 02:09 am, Geoffrey Young wrote: > >>>>It looks like 2.1 is going through a big update tonight, > >>>>and the cvs sources are unstable. > >>>> > >>>>If you have a chance, can you let me know when it is > >>>>usable again? > > my nightly build last night went off without a hitch: > > /apache/2.1/worker/perl-5.8.4/bin/httpd -d > /src/mod_perl-2.0/ModPerl-Registry/t -f > /src/mod_perl-2.0/ModPerl-Registry/t/conf/httpd.conf -D APACHE2 -D > PERL_USEITHREADS > using Apache/2.1.0-dev (worker MPM) > > ... > All tests successful > > $ /apache/2.1/worker/perl-5.8.4/bin/httpd -V > Server version: Apache/2.1.0-dev > Server built: Apr 28 2004 03:10:55 > Server's Module Magic Number: 20040425:0 > > are you still having a problem?
Geoff - I solved my problem yesterday, I guess my reply didn't get to you: > > The things I am seeing are incorrect versions of mods when > > I test mod_perl: expecting 20040425 got 20030821. Got those > > in mod_apreq.so and mod_authn.so. > > oh, that's different. it probably means that your test is picking up on an > old apache 2.0 build instead of the one you are specifying with -apxs. No so. I have solved that problem (which I ran into last month) with a set of 'iron clad' scripts that keep every version I have (2.0 2.0-debug 2.1 2.1-debug) isolated from the other versions. I tracked down the 'problem'. I did not have an error message for mod_authn.so (I misread the log due to no sleep), only with mod_apreq.so. Guess what? 'mod_apreq.so' recently went bye-bye so mod_apreq.so from the last compile of Apache2.1 was picked up by the mod_perl Apache::Test configuration builder, and, of course, it was out-of-date. I have fixed my scripts to nuke all .so s prior to install. All is well. Again, thank you for your help. Aloha => Beau; --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
