Re: perl modules not running after 'minor' change

[Geoffrey Young]

>> That sounds like a job for Apache to do. Apache knows what modules are
>> compiled in, so it can check that list before trying to LoadModule.
>> You may want to suggest that to the Apache developers. Most likely any
>> Apache module suffers from this problem.
> 
> 
> I thought that's what I was doing by stating it explicitly like that in
> this list.

this is the mod_perl list, for discussion of mod_perl-type things.  as stas
mentioned, the problem that you are discussing is more of a core Apache
thing and really has nothing to do with mod_perl - it could happen to any
extension module.

that said, I'll give it a look this week and see what can be done to help
out everyone over in apache-land.

--Geoff

-- 
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

Re: [mp2] Known problem with mod_perl 1.99_16 on FreeBSD 5 ?

[Carl Brewer]

Stas Bekman wrote:

that seems to be a MakeMaker bug on some BSDs. Please see:
http://rt.cpan.org/NoAuth/Bug.html?id=7417
The solution seems to be to use gmake. At least it worked for Carl on 
NetBSD.
It works for me with gmake, yes.
There's another problem I haven't had time yet to report though,
but it may be relevant - it doesn't find ThreadMutex.pm
at (g)make install time.  I just commented the ThreadMutex
line out of the makefile and it seems ok to me, but that may not
be ideal.
Carl
--
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