On Sat, Sep 13, 2003 at 05:11:07PM -0500, Jason L. Schwab wrote: > Heya Folks; > > System Specs: > > FreeBSD 4.8-STABLE > OpenSSL 0.9.7a (OS Installed) > Apache 1.3.27 > Mod_Perl 1.28 > Mod_SSL 1.3.28 / 2.8.15 > Perl 5.8.0 (ports/lang/perl58 installed) > (use.perl port) > > I have tried many, many ways to get mod_ssl and mod_perl to > compile on many servers, all with near same configurations, > with absolutely no luck.
That's funny. Works fine for me just compiling from ports. You need
to start by installing the apache13-modssl port: mod_ssl can't be
installed as a stand-alone module to load into plain apache, and
furthermore any other modules need to be compiled against the
apache13-modssl combination.
A very useful trick is to add:
APACHE_PORT=${PORTSDIR}/www/apache13-modssl
into /etc/make.conf, which convinces most apache related ports to
depend on the mod_ssl-ified apache.
> All I can ever to get to compile is either just mod_ssl, just
> mod_perl, and with same configurtation options, I can get it
> to say and show and compile SSL and modperl, but "httpd -l"
> shows no mod_perl ? only mod_ssl, or vice versa!
httpd -l only shows the *compiled in* modules, not the dynamically
loaded modules. My httpd with both mod_perl and mod_ssl produces:
% httpd -l
Compiled-in modules:
http_core.c
mod_so.c
> Altho, when the above happens, apache's configure shows it
> adding both SSL and ModPerl uses Config/End Config/Start,
> normal stuff, and it even goes thro the directories for the
> compile and has no errors.
If you can add mod_ssl or mod_perl configuration directives to
httpd.conf (outside any <IfModule ..></IfModule> block and run
'apachectl configtest' without apache complaining, that means your
apache does have the required support.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
pgp00000.pgp
Description: PGP signature
