>> 1. Should I be able to safely run 'make install' now?
>
> Yup.
I noticed when omitting SSL from the Apache build (which resulted in a
successful 'make') that a bunch of Apache 'utility' binaries are linked
after httpd is built (a half-dozen or so). So, I'm assuming 'make install'
will install Apache, but not these utility binaries. I guess that's kind of
obvious; just checking.
> why in the world did you build your perl statically linked?
Are you wondering why I'm not using mod_perl via DSO? (... versus
statically linking it into Apache?)
Or are you talking about my vanilla Perl installation on my machine?
I don't believe I did anything unusual when upgrading my Perl. FreeBSD 4.8,
the latest production release, comes with Perl 5.005_03, so I upgraded to
the latest Perl before installing anything else. I used a vanilla
installation (documented in the INSTALL file in the distribution):
fetch http://www.cpan.org/src/perl-5.8.1.tar.gz
tar -xzf perl-5.8.1.tar.gz
cd perl-5.8.1
rm -f config.sh Policy.sh
sh Configure -de
make
make test
make install
If it's the former (i.e., you're wondering why I'm not using mod_perl via
DSO), well, heh... I had read that statically linked mod_perl was more
secure, and faster. Once my configuration is up, I don't expect many
changes, so the 'bother' of building Apache each time I want a change isn't
a big deal.
But, maybe you're talking about Perl and not mod_perl/Apache. If that's the
case, what did I do wrong? Something when I installed Perl 5.8.1?
