d) Another useful tip - that may seem a bit stupid, but which I found useful - was to check after completing the installation process that the 'modules' directory under '/usr/local/apache2' (or whatever) contained the file 'mod_perl.so'. In my first few attempts at installation this was useful to see if things had actually been installed in the right place.
I'm not sure I'm following this one. Did you have a case that it wasn't installed there?
Yes... I'm trying to recall the details but I think it was because I had set the MP_AP_PREFIX= to the wrong location (...my earlier comment about not understanding what it should be set to!). The install said completed without coughing, and when I looked hopefully in the /modules/ directory of the Apache installation tree the 'mod_perl.so' was absent. So I used that method to check whether I was at least on the right track with the installation.
I tried it a couple of times before I realised what I might be doing wrong... =)
This is something that needs to be dealt in the code, not documentation. If you told it to install things somewhere and it has failed the installer should abort and report the error. If it doesn't than it's a bug.
But I think your problem is totally different. You whouls be using MP_APXS and not MP_AP_PREFIX. The latter is used only to build a static Apache/mod_perl.
-- __________________________________________________________________ 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
