httpd-test-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache TestConfigPerl.pm
Date Fri, 28 Mar 2003 04:50:13 GMT
stas        2003/03/27 20:50:13

  Modified:    perl-framework/Apache-Test/lib/Apache TestConfigPerl.pm
  Log:
  a minor fix and more problems to resolve
  
  Revision  Changes    Path
  1.68      +6 -0      httpd-test/perl-framework/Apache-Test/lib/Apache/TestConfigPerl.pm
  
  Index: TestConfigPerl.pm
  ===================================================================
  RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/TestConfigPerl.pm,v
  retrieving revision 1.67
  retrieving revision 1.68
  diff -u -r1.67 -r1.68
  --- TestConfigPerl.pm	28 Mar 2003 04:13:14 -0000	1.67
  +++ TestConfigPerl.pm	28 Mar 2003 04:50:12 -0000	1.68
  @@ -21,6 +21,12 @@
       if ($server->{rev} >= 2) {
           if (my $build_config = $self->modperl_build_config()) {
               $libname = $build_config->{MODPERL_LIB_SHARED};
  +            $vars->{libmodperl} ||= $self->find_apache_module($libname);
  +            # XXX: we have a problem with several perl trees pointing
  +            # to the same httpd tree. So it's possible that we
  +            # configure the test suite to run with mod_perl.so built
  +            # against perl which it wasn't built with. Should we use
  +            # something like ldd to check the match?
           }
           else {
               # XXX: can we test whether mod_perl was linked statically
  
  
  

Mime
View raw message