I've noticed a problem for the past version or two of mod_perl, which still seems to be present in _16. I'm calling Makefile.PL like so:

  perl Makefile.PL MP_COMPAT_1X=1 MP_AP_PREFIX=../httpd-2.0.50

and yet the generated Makefile has:

INC = -I/users2/dwilga/mod_perl-1.99_16/src/modules/perl -I/users2/dwilga/mod_perl-1.99_16/xs -I/users2/dwilga/mod_perl-1.99_14/../httpd-2.0.47/include -I/users2/dwilga/mod_perl-1.99_14/../httpd-2.0.47/srclib/apr/include -I/users2/dwilga/mod_perl-1.99_14/../httpd-2.0.47/srclib/apr-util/include -I/users2/dwilga/mod_perl-1.99_14/../httpd-2.0.47/os/unix

Note the references to 2.0.47. I do have a 2.0.47 tree there, but that's not what I specified in the commandline. It seems to be keeping settings from a previous version.

OK, so next I figured I'd let it ask me the path, so I left off MP_AP_PREFIX:

% perl Makefile.PL MP_COMPAT_1X=1
Reading Makefile.PL args from @ARGV
   MP_COMPAT_1X = 1
Configure mod_perl with /users2/dwilga/mod_perl-1.99_14/../httpd-2.0.47? [y] n
Configuring Apache/2.0.47 mod_perl/1.99_16 Perl/v5.8.0
WARNING: NO_META is not a known parameter.
'NO_META' is not a known MakeMaker parameter name.
[   info] generating script t/TEST
Writing Makefile for Apache::Test
[   info] generating script t/TEST
Writing Makefile for ModPerl::Registry
Writing Makefile for APR::Base64
Writing Makefile for APR::Brigade
...

Notice how I said "n", yet it went ahead and generated the makefiles anyway.

--
Dan Wilga                                         [EMAIL PROTECTED]
Web Technology Specialist                     http://www.mtholyoke.edu
Mount Holyoke College                                Tel: 413-538-3027
South Hadley, MA  01075            "Who left the cake out in the rain?"

--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html



Reply via email to