Stas Bekman wrote:
> > > 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.
>
> The definitive answer is there for at least 2 years: "If in doubt compile
> statically", which covers Solaris as well. Why having a special case?
So what is the point of having DSO at all then?
The question was 'How do I build on Solaris with DSO?', the answer was
'Build perl to use the system malloc', I don't see what the problem with
that is.
--
Alan Burlison
--
$ head -1 /dev/bollocks
repurpose collaborative focus groups, going forwards
