On Thu, 16 Aug 2001, Alan Burlison wrote:
> 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.
You are right, it was my mistake. I read the solution to the problem was
not to build it as DSO. (mail overload problem :( ) I'll add this note
regarding Solaris.
I think the best thing would be if somebody who has an extensive DSO build
experience across many platforms could summarize the problems, so we can
put it into the guide. Personally I always build my production servers as
static, so I only rely on comments from others.
Currently what I've is:
* How do I build on Solaris with DSO?
=> Build perl and mod_perl using the system malloc
* My server leaks memory on restart with DSO
=> don't use DSO
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://localhost/ http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
