Mailing-List: contact modperl-help@apache.org; run by ezmlm
Message-ID: <38E0D5A0.3DFD40DB@gina.net>
Date: Tue, 28 Mar 2000 10:54:08 -0500
From: Aaron Johnson <solution@gina.net>
MIME-Version: 1.0
To: "'modperl@apache.org'" <modperl@apache.org>
CC: Gerald Richter <richter@ecos.de>
Subject: Perl 5.6 issues?
References: <ADA279A216AFD211AD4000902732B733020D577B@cmhmail.symix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have a sucessfully compiled on Linux (Slackware 3.5) 5.6/1.22/1.3.12 with no
modifications.  All these items worked fine together with 100% pass rate on
tests.

mod_perl - perl Makefile.PL EVERYTHING=1
NON DSO

I have it installed and serving pages with numerous Perl modules.

The two remanining issues for me are HTML::Embperl and SSI.

I have been in contact with Gerald Richter (the author of HTML::Embperl) and he
is looking into it.  See the embperl@perl.apache.org mailling list for more
information.

So until that is resolved each child can only serve one request and then dies.
Which is not good if you are running a high traffic site.

I have also noticed that SSI pages are not working.  I notice in the compile
that it says USE_PERL_SSI or something similar, does that in fact mean that SSI
is handled by mod_perl on a mod_perl enabled httpd?  It handles the first SSI
fine, but the page that is called has SSIs inside of it and these cause the page
to "stop". I removed these and then when the included page finishes it does not
return and finish the opening page it "stops" at the end of the include file.  I
believe it causes a segmentation fault and kills the apache child at this point.

Could the segmentation fault be due to the mod_perl code (or more likely changes
in the Perl 5.6 code) and in turn cause the Embperl problems? The Embperl issue
is on file cleanup/close so I am thinking that the same area is handling the
clean up on the SSI page, but the mod_perl test suite shows a pass on SSI. Of
course I am totally guessing here.  (See
http://www.mail-archive.com/embperl@perl.apache.org/ for more information. The
subject is "Compile problems")

I tried the compile with Apache 1.3.9 and it had the same results.

Aaron Johnson

Charles Day wrote:

> Hmmmm, I removed .../apache/src/modules and it failed "couldn't find
> .../apache/src/modules/standard directory"
>
> Here was my apache configure script...
>
> ./configure \
> --prefix=/usr/local/apache \
> --activate-module=src/modules/perl/libperl.a
>
> There is no libperl.a and here's the ole error message...
>
> mod_perl.c: In function `perl_handler':
> mod_perl.c:783: `PL_siggv' undeclared (first use in this function)
> mod_perl.c:783: (Each undeclared identifier is reported only once
> mod_perl.c:783: for each function it appears in.)
> make[4]: *** [mod_perl.o] Error 1
> make[3]: *** [all] Error 1
> make[2]: *** [subdirs] Error 1
> make[2]: Leaving directory `/usr/src/apache_1.3.12/src'
> make[1]: *** [build-std] Error 2
> make[1]: Leaving directory `/usr/src/apache_1.3.12'
> make: *** [build] Error 2
>
> There is a libperl.module, so I tried agian, with...
>
> --acitvate-module=src/modules/perl/libperl.module
>
> and low an behold, I get an error message "coundn't find libperl.a"
>
> LOL
>
> It installs fine without this --activate-module line, but I think I need
> this.
>
> I'm trying AddModule modules/perl/libperl.a into Configuration now.
>
> apache 1.3.12
> mod_perl 1.21
> perl 5.6
>
> >
> > -----Original Message-----
> > From: Jim Serio [mailto:jim@rollercoaster.com]
> > Sent: Monday, March 27, 2000 4:08 PM
> > To: Charles Day
> > Cc: modperl@apache.org
> > Subject: Re: perl 5.6/mod_perl 1.22/apache 1.3.12
> >
> >
> > > Just spent half the day trying marry these 3.  mod_perl doesn't build.
> > > DSO/apxs errors as described by others.  Went back to 1.21, apache
> doesn't
> > > build, PL_siggv errors as described by others.  Don't know what to do
> with
> > > the modperl 2.0XXX.  I think I'll head back to Mr. stable 5.00503.  Sure
> > > wish I knew C.
> >
> > I had initial problems with Apache 1.3.12 and mod_perl 1.21
> > but after removing the perl modules dir and installing
> > mod_perl 1.22 things compiled without any problems. I
> > suggest you try a clean Apache and mod_perl source tree.
> >
> > Jim
> >
>
> --
> Jim Serio - jim@rollercoaster.com
> Producer, World of Coasters