FW: Installation help [mod_perl 2.0.5/apache 2.2.17/perl-5.12.3]

"Szekeres, Edward" <[email protected]>
Newsgroups gmane.comp.apache.mod-perl
Message-ID <E56A83649BC95043A68560768DE7E8820210EA82@AMERMAIL02.PERKINELMER.NET>
I wanted to follow up and say that while below seemed to be a solution, it seems to have been a fluke as my attempt to replicate has unfortunately not been successful.  I wanted to go back in enable the mod_ssl and so I repeated the exact steps, though without success.  I have no idea why the one attempt seems to have proceeded fine.

-edward

-----Original Message-----
From: Szekeres, Edward 
Sent: Monday, April 18, 2011 4:48 PM
To: [email protected]
Subject: FW: Installation help [mod_perl 2.0.5/apache 2.2.17/perl-5.12.3]

FYI

Wanted to let you know I accidently stumbled on a something that worked,  I had noticed that if I ran the mod_perl config twice, the second time it ran it would not show that apr directory-not-found error, however the make would fail with some APR related errors,  however,  if I added the "--with-included-apr" option to the MP_AP_CONFIGURE option to the mod_perl config, then again ran the command twice, the first time it would fail with the directory not found error as before, the second time it ran through completely, *BUT* this time 'make' ran without a problem and the rest of the process ran error free.  I then checked with 'httpd -l' and mod_perl.c was listed in the built in module list.  I am trying to test the now running web service to see if everything functions.

Not quite sure what that all meant....but it seems I now have a static  linked version

> -----Original Message-----
> From: Fred Moyer [mailto:[email protected]]
> Sent: Monday, April 18, 2011 2:44 PM
> To: Szekeres, Edward
> Cc: [email protected]
> Subject: Re: Installation help [mod_perl 2.0.5/apache 
> 2.2.17/perl-5.12.3]
>
> On Mon, Apr 18, 2011 at 9:46 AM, Szekeres, Edward <[email protected]> wrote:
>> Thanks for your reply....clarifications
>
> For what it is worth, I'd suggest building mp2 as a shared object; this approach is very well tested.  You may be able to build as a static module, but that can take some additional effort, and that build option is not as widely tested.
>
> Building as a dso is simple - 'perl Makefile.PL MP_APXS=/usr/local/bin/apxs', or just 'perl Makefile.PL' if your apxs is in $ENV{PATH}.  This requires that you build Apache outside the mod_perl build, but for that I usually './configure --enable-so --with-included-apr --prefix=/path/to/my/apache'.
>
>>
>> 1) Perl 5.12.3 was compiled without thread support as per the 
>> mod_perl
>> 2.0 installation directions
>>
>> 2) I have tried adding the "--with-included-apr" option without luck
>>
>> 2) As per the mod_perl documentation for static I am not 
>> pre-compiling Apache but was allowing the mod_perl 2.0 process to 
>> handle that
>>
>> 3) I  was trying to match a pre-existing configuration which was using Apache 1.3 with  mod_perl 1.0 statically linked in.  While it would be preferred to keep the configuration the same, I am not sure it is mandatory.
>>
>> 4) what is also interesting is if I repeat the mod_perl configuration command again, I do not get that "Can't find apr include/ directory" error, and the config proceeds fine, however the make just throws a bunch of errors which seem to be apr related...
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.