Philip,
thanks a lot for this thorough and exhaustive answer!
Philip M. Gollucci schrieb:
Michael Ludwig wrote:
So, to summarize: The mod_perl DSO depends on the particular versions of
Perl and Apache.
The modules in the Apache2:: namespace
most definitely dpends on libperl.so, httpd, apr, apr-util, and
mod_perl.so
The modules in the Apache2:: namespace depend on
libapreq2.so and mod_apreq2.so + all the above ones.
Plus, maybe incidentally, on libexpat, as shown in my ldd output:
/usr/local/apache22w/lib/libapr-1.so.0 (0xb7eb8000)
/usr/local/apache22w/lib/libaprutil-1.so.0
/usr/local/apache22w/lib/libexpat.so.0
(which looks like an error in the configure/build logic):
/usr/local/src/libapreq2-2.08/library/.libs/libapreq2.so.3
we [joes] just fixed this though it doesn't affect everyone. Its will
be in the next release which will be soonish
Thanks.
Now, what happens if I am going to install a new Apache
2.2/prefork with mod_perl in addition to the already existing
Apache 2.2/worker with mod_perl? The new mod_perl modules are
going to clobber the existing one, probably rendering the old
mod_perl useless by supplanting their own versions linked to the
prefork MPM libraries, and I imagine the worker MPM won't be happy
when being asked to interact with these. True?
Correct, you get to play magical paths.
Consider yourself a developer now and the following tree:
Thanks for the following [snipped] as well - I need some more time to
understand it.
Michael Ludwig
