Contrary to what has been suggested elsewhere in this thread, I would not suggest using an rpm to install mod_perl; thisi s because the rpm installs mod_perl as a DSO, which has been shown to cause problems down the line.

Yes, you will need LWP installed. After that -- well, ordinarily I'd suggest you peruse the most magnificent mod_perl Guide, but I've found something which is an order of magnitude easier -- Apache Toolbox. Just turn on the mod_perl option in the menu, sit back, and relax. 95% of the time, that's all that it'll take. Give it a try.

If you decide not to to that, my only guess is that the directory is not called apache_1.3, but apache_1.3.xx, Take a gander at the getting your feet wet section of the Guide for more details.

Update: In answer to fuzzyping, check out the pros and cons of using DSO, as well as the section on using RPM to install mod_perl. See this message (and reply) sent on the mod_perl list today for a real-world example of DSO causing havoc with mod_perl. Other sources confirm this; however, I thought there was something more specific in the Guide warning about the dangers of DSO, but I can't seem to find it now.

perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'

While I can appreciate the effort you've put into researching this, I can't identify with the drawbacks of mod_perl DSO vs. the advantages/conveniences of running them. Particularly if you're not having any problems with them at all. The worst disadvantage I could pull out of the guide is probably the 20% slowdown at server startup. So what?

With respect to the rest of the guide cons, most of those are very platform-specific, and don't sound applicable to Linux. As far as the mod_perl-list thread is concerned, the reader lays it out there... yes, it appears this individual may be having problems with DSO and mod_perl, but the alternative is to compile Apache without any DSO support? Come on!

It appears that you're applying a handful of individual's specific problems to the whole DSO bunch. I run DSO's pretty religiously without any problems (granted, I'm also not hosting anything with serious volume), as well as thousands of other folks out there.

Again, just my $0.02. Feel free to disagree. :)

-fp

As far as the mod_perl-list thread is concerned, the reader lays it out there... yes, it appears this individual may be having problems with DSO and mod_perl, but the alternative is to compile Apache without any DSO support? Come on!

Ahem. ;>

This "mod_perl DSO == bad" approach that I am coming from is not so much the result of an evening of research, but more the result of over a year lurking on the mod_perl lists. You are not the first to challenge that most of the eviednce against DSOs is anecdotal -- again, see the list.

Also just my two cents. Personally, I have seen no reason not to compile it statically, and some personal experience with segfaults caused by mod_perl as a DSO. Hence, I will continue to err on the side of caution (and also speed :) and build mod_perl in statically.

perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'