I appreciate you taking a look. I actually fixed that part with
symlinks. I attached the wrong make test.
On Jun 10, 2009, at 1:40 PM, Adam Prime wrote:
Sean Thorne wrote:
Hi,
I don't know whats wrong, but my hosting environment recently
pushed an update of glibc and pthread to all of m
Hi all,
I have the same problem in an HP PARISC and with apache 2.2.11 and
modperl2.0.4 and perl 5.8.9. The workaround of Mario was eficient but not
enough to complete the static compile of the mod_perl if fact I had new
errors which are:
libtool: link: warning: this platform does not lik
Hi,
Sorry, It is 2.2.11
Thanks
2009/6/11, Randy Kobes :
>
> On Wed, Jun 10, 2009 at 12:04 PM, mmm zzz<3mmm...@gmail.com> wrote:
> > Hi again,
> >
> > Yes you gessed right there is problem on test and this is what i get :
> >
> > make test
> > cd "src/modules/perl" && make
> [ ... ]
>
> > /
On Wed, Jun 10, 2009 at 12:04 PM, mmm zzz<3mmm...@gmail.com> wrote:
> Hi again,
>
> Yes you gessed right there is problem on test and this is what i get :
>
> make test
> cd "src/modules/perl" && make
[ ... ]
> /Installation_pakage/PARISCapache2.2/bin/httpd -d
> /Compiling_package/apacheMo
I'm working with some old perl code that was previously running under
modperl 1.x, but was recently updated for 2.x. There is a fairly severe
memory leak somewhere in this code, but I'm having a hell of a time
tracking it down.
The problem is that I don't know which of our many perl files is causi