> > AB> Untrue. We ship mod_perl in Solaris 8 as a DSO, and it works
fine.
> > I apologize. Let me qualify my original statement. In general, you
> > want to compile mod_perl statically on Solaris 2.6 or 2.7 because
> > in many instances, it core dumps when built as a DSO. FWIW, my
> > particular experiences were with Perl 5.005_03 and 5.6.0, mod_perl
> > 1.24 and 1.25, and Apache 1.3.12, 1.3.14, 1.3.17, and 1.3.19 under
> > Solaris 2.6 (both Sparc and Intel) and 2.7 (Intel only).
> No need for an apology :-) The trick is to build perl using the
> Solaris malloc (-Dusemymalloc as a flag to Configure), then apache,
> mod_perl and perl all agree on who manages memory.
Might I suggest that this golden piece of information find it's way into the
guide? It's so rare to see a DEFINITIVE answer to one of the many ("YMMV!"
:-)exceptions to the vanilla mod_perl build process.
L8r,
Rob
#!/usr/bin/perl -w
use Disclaimer qw/:standard/;
