On Aug 6, 2004, at 4:27 PM, Stas Bekman wrote:
Yes, it's a confusing explanation. How about this rewrite:
Much better. Thanks for the confirmation. Just a few nits:
First check which malloc Perl was built with, by running:
% perl -V:usemymalloc
If you get:
usemymalloc='n';
it means that Perl is using the system malloc, so mod_perl will work fine as DSO.
If you get:
usemymalloc='y';
it means that Perl is using its own malloc. If you are running Perl older than 5.6.0, you must rebuild Perl with C<-Uusemymalloc>.
If you are running Perl 5.6.0 or higher, you must make sure that you have the binary compatibility with Perl 5005 turned off. To find out, run:
% perl -V:bincompat5005
If you get:
bincompat5005='define';
then you must rebuild Perl with C<-Ubincompat5005>. Then you can continue
using Perl's malloc if that's a better choice for your OS.
Regards,
David
smime.p7s
Description: S/MIME cryptographic signature
