/tmp> ldd /home/stas/httpd/prefork/modules/mod_perl.so | grep libperl.so
libperl.so => /home/stas/perl/blead-ithread/lib/5.9.0/i686-linux-thread-multi/CORE/libperl.so (0x40030000)
/tmp> ldd ~/perl/blead-ithread/bin/perl | grep libperl.so
libperl.so => /home/stas/perl/blead-ithread/lib/5.9.0/i686-linux-thread-multi/CORE/libperl.so (0x40014000)
and compare if the two point to the same file.
Alternative solutions I could think of:
- do binary compatibility test at mod_perl.so boot time. How can we do that?
(test the perl version and path to libperl.so?)
sometimes mod_perl.so from the same perl with different parameters (e.g. w/ and w/o ithreads) will boot OK, but won't work. In other cases mod_perl.so simply won't load, so it'll fail before we can do the testing.
- test the timestamp of the mod_perl.so and mod_perl.pm if they differ wildly there must a problem. But I guess this approach is not very practical.
- install some signature along with mod_perl.so. e.g. could create an MD5 hash of libperl.so install it next to mod_perl.so (in mod_perl.sig and check it at configure time). This looks like a practical solution.
Any other ideas?
__________________________________________________________________ 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]
