We're running perl 5.005_03 on Solaris 2.6/sparc.  When I go to build
mod_perl as a DSO, I get:

************* ERROR *************

  Your current configuration will most likely trigger core dumps,
suggestions:
   *) Do not configure mod_perl as a DSO
   *) Upgrade your Perl version to 5.6.0 or higher (w/ -Ubincompat5005)
   *) Configure Perl with -Uusemymalloc (not recommended for performance)


************* ERROR *************

We're not in a position to upgrade perl or reconfigure perl.  So I can't
build mod_perl as a DSO.

My options are (in order of preference):
- build apache with mod_perl (statically) and mod_so.  Then to load mod_jk
with apxs.
- build apache with mod_perl and mod_jk statically.
- run two apache instances.  The first one will have mod_so and mod_jk and
will handle requests for servlets and static pages.  The second will have
mod_perl and will handle perl requests.

If you, or anyone else, has any advice, I'd be stoked.

Thanks,
* * * John


-----Original Message-----
From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 05, 2001 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: mod_jk and mod_perl


I've run both mod_jk and mod_perl as dynamically linked modules in the past,
but not statically. The dynamic modules were very easy to get running.

Any reason it has to be statically compiled?

Thanks,
--jeff

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 05, 2001 3:48 PM
Subject: mod_jk and mod_perl


> Hello,
>
> I'm trying to build a statically linked version of apache v1.3.19 with
> mod_jk (from tomcat v3.2.1) and mod_perl v1.25 for Solaris 2.6/sparc.  Has
> anyone successfully done this before?  I can build apache with mod_jk and
> apache with mod_perl, but I haven't been able to build apache with both
> modules.  I've searched this mailing list and several others and have made
> no progress.  My next step is to deconstruct the mod_jk makefile to fit
the
> source into $APACHE_SRC/src/modules/jk.  Any hints are appreciated.
>
> Thanks,
> * * * John Ubante
>

Reply via email to