We get more and more bug reports with obscure failures when the real reason is that wrong mp2 libraries get loaded. e.g., older builds, incompatible builds. I thought it'd be only us developers, hit by this issue, but apparently the problem is relevant for normal users as well. Hence, I'm thinking of adding the bootstrapping magic check similar to what Apache does with its MMN.

In the mod_perl 2.0 case it's not enough to check MMN, but we have to include information like whether ithreads were enabled or not. e.g. we could md5 the perl binary? this will probably be a problem if mod_perl build on one machine but used on another. So may be we just need to compile a set of options that make the difference whether a library is compatible or not.

Comments?

__________________________________________________________________
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


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to