Stephen Jungels wrote:
may be it was compiled statically into httpd? try:

nm /usr/local/apache/bin/httpd | grep apr_snprintf


You're right.  In fact, the symbol that caused the original problem is right
there in httpd:

[EMAIL PROTECTED]:/usr/local/mod_perl-1.99_17# nm /usr/local/apache/bin/httpd
| grep apr_pool_cleanup_null
100be104 G ap_hack_apr_pool_cleanup_null
1008e6e8 T apr_pool_cleanup_null

Well, I don't really know, but it occurs to me that there may be some issue
with installing mod_perl as a DSO when apache is compiled statically, so I
think I will look in to statically compiling mod_perl.

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

I noticed during the
rebuild that apache configure thinks my linker does not support shared
objects (it does) and builds statically as a result.

Submit a bug report to httpd-dev?

Anyway, Stas, thanks
for helping me narrow this down.  I will keep the list posted if anything
else comes up that is mod_perl related.

you're welcome, Stephen.

[1] http://perl.apache.org/docs/2.0/user/install/install.html#Static_mod_perl

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



Reply via email to