Stas Bekman wrote:
So it sounds like a loader problem, since mod_perl.so is loaded after httpd is in the memory, so there shouldn't be a problem finding the apr_pool_cleanup_null symbol.
Of course you could build mod_perl statically [1] and then there shouldn't be no problems (but it'd be also nice to figure out what's the problem with your setup):
Yes, I'm not giving up yet. I also would prefer to track the bug down rather than work around it, especially if you think mod_perl.so ought to work with a statically compiled httpd. In the meantime I will statically compile mod_perl just to get something working.
I've never tried linking apr statically, but I see no reason why it shouldn't work. The only reason I could see it not working if the linker/loader mangles the symbols so that DSO modules can't use those. But you will need to dig into your loader docs for that.
Of course, the loader has worked so well for me so many times without my even noticing it, that I'm reluctant to conclude there is anything wrong with it. But who knows.
I'd suggest the following plan: Get some mod_foo that works with Apache2 and relies on APR and try to build it as DSO and use it (.e.g some module that comes with Apache2, mod_proxy, etc). Hopefully you will get the same problem when you try to load it. If so you can ask for help at the httpd-dev list. Why do I suggest to make things complicated? Because mentioning mod_perl on the httpd-dev list ensures that you question will be ignored.
-- __________________________________________________________________ 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
-- 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
