Another thing about installation guide: http://perl.apache.org/docs/1.0/guide/install.html#mod_perl_and_mod_php 1) Configure Apache.
% cd apache_1.3.xx % ./configure --prefix=/usr/local/etc/httpd Why should I do this, I allways skip this step and everything fine. I don't understand why I should configure Apache before modules if I use APACI interface which primary advantage is ability to do it later.
it's has been awhile since i've last done that, but that step was needed at that time. perhaps things have changed in the last few years, so it's no longer required. but since we always have users who try to build older versions, let's keep it there, as there is no harm in it. may be adding a comment that the 1st step may not be needed with the recent packages is due.
http://perl.apache.org/docs/1.0/guide/install.html#toc_The_Flexible_Way $ cd mod_perl-1.xx $ perl Makefile.PL \ APACHE_SRC=../apache_1.3.xx/src \ NO_HTTPD=1 \ USE_APACI=1 \ PREP_HTTPD=1 \ EVERYTHING=1 \ [...] $ make $ make install $ cd ..
This isn't flexible way. If I run 'make install' before apache build and mod_perl test it could overwrite current files. Am I wrong here? What to do if apache build will fail and I have to wait for fix?
overwrite what files? previous mod_perl build? sure, don't run 'make install' then. you will have exactly the same problem with any other scenario where each module needs to run its own 'make install'.
__________________________________________________________________ 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
-- 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
