Arshavir Grigorian wrote:
And it's correct. I'm using --enable-module inside APACI_ARGS all the time at the *command* line, as the section suggests.Hi,I was trying to build Apache 1.3.27 + mod_perl 1.27 from the mod_perl tree. Dir structure as follows: /usr/local/apache2-19 /use/local/apache2-19/build /use/local/apache2-19/build/apache_1.3.27 /use/local/apache2-19/build/mod_perl-1.27 So, following the suggestion from http://perl.apache.org/docs/1.0/guide/install.html#APACI_ARGS that one can pass *any* arguments to the Apache ./configure through the APACI_ARGS directive, I placed the following lines into
/use/local/apache2-19/build/makepl_args.mod_perlHowever there must be a glitch in the way a special makepl_args.mod_perl is processed. If someone can try to resolve a problem and post a patch, that would be very helpful.
APACHE_SRC=../apache_1.3.27/src DO_HTTPD=1 USE_APACI=1 EVERYTHING=1 \
APACI_ARGS='--prefix=/usr/local/apache2-19, --enable-module=dir'
This generated some errors during the configure process
cd /use/local/apache2-19/build/mod_perl-1.27/
make clean
perl Makefile.pl
...
'--ENABLE-MODULE' is not a known MakeMaker parameter name.
...
I then discovered ADD_MODULE parameter and used that instead of using the Apache's --enable-module parameter.
Correct me I am wrong, but I think the guide's section on using the
APACI_ARGS parameter should say something about not being able to
use '--enable-module' there, and have a pointer to the ADD_MODULE parameter.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com