Re^6: Trying to use Apache2::Module throws an Apache exception

Sorry, it's there. Omission while trying to craft something legible. I've filed a bug on the mod_perl2 CPAN. Is epel the one true source for the mod_perl RPM? I'm torn as to whether to build my own RPM. I got 25% of the way there last night. It's been 20 years since I did that! I suppose I could try on my Ubuntu VM.

Comment on Re^6: Trying to use Apache2::Module throws an Apache exception

Replies are listed 'Best First'.
Re^7: Trying to use Apache2::Module throws an Apache exception by hippo (Archbishop) on Sep 08, 2017 at 10:24 UTC
Is epel the one true source for the mod_perl RPM? Sorry, I have no idea. Having been bitten by a problematic RedHat mod_perl RPM many years ago I have studiously avoided them since and have always compiled from source. (I rarely use the stock RedHat Apache either and much prefer to build that from source too) For those following along, here's the bug report raised by davehodg. You might want to mention there that you've used PerlLoadModule otherwise that's what respondents would likely suggest.	[reply]
Re^8: Trying to use Apache2::Module throws an Apache exception by davehodg (Acolyte) on Sep 08, 2017 at 10:34 UTC
At the moment it's acutally: `<Perl> use lib qw(/iop/common/lib /iop/journals/xs/Journals/Config2 /iop/mail +q/lib /iop/journals/lib); use Journals::Trans; ... </Perl>` [download] But it's been PerlLoadModule with the same result.	[reply] [d/l]
Re^8: Trying to use Apache2::Module throws an Apache exception by davehodg (Acolyte) on Sep 13, 2017 at 13:58 UTC
I grabbed the SRPM, unpacked it, commented out the assertion, rebuilt it, installed all the RPMs, re-installed mod_perl (why?) and it's fine. Still want to know why the module count was out of whack.	[reply]