I'm going to follow your instructions, thank you.
One question, though, since it seems you're adding args to a file that gets
passed to mod_perl's build process (which in turn builds httpd): how do
you add/activate other modules to apache in this manner. PHP is a DSO
(for me) so that's solved. But I have some others, for example one of my
and so forth. I may have had the build process incorrect in the beginning,
where first I would run a script to do:
I know that certain configuration parameters need to be set before you
build Apache (like the Layout, which I customize).
Thanks for your help.
At 12:01 PM 5/26/2003, you wrote:
>Please keep it on the list.
>On Mon, 26 May 2003, Forrest Aldrich wrote:
> > I'm using whatever is in CVS at the moment. The Changes file indicates
> > this is version 1.27_01-dev.
>Well that *should* be OK, but I have to wonder why you're doing it
>that way. It can only make things more complicated. Why not just
>grab the latest tarballs?
> > trying to figure out how to get it statically-linked, as opposed to DSO --
> > I've looked around for simple directions out there and haven't run into
>Have you not seen the Guide? Heaven knows it's mentioned enough on this List,
>and on the mod_perl home page at http://perl.apache.org
>It's quite simple to build mod_perl statically.
>First you may need to stop any existing Apache - things get confusing
>if you accidentally try to run two at once. (They're confusing enough
>if you do it on purpose :). Then I'd recommend taking all the junk you
>now have in /usr/local/apache and hiding it someplace safe for now. I'm
>assuming you're building with the apache binaries, config files etc. under
>/usr/local/apache, but you might not be. If not then get rid of them from
>wherever they are. (I'd just move them, not delete them. :) Then:
>0. mkdir -p /home/forrest/src
>1. cd /home/forrest/src
>2. tar xzvf .../mod_perl-1.27.tar.gz
>3. tar xzvf .../apache_1.3.27.tar.gz
>4. cd mod_perl-1.27
>5. cp attached_file makepl_args.mod_perl
>6. perl Makefile.PL
>9. make install
>10. cd ../apache_1.3.27
>11. make install
>Now you should be able to start Apache and see a message in the
>error_log telling you what it was you started. Then the configuration
>fun begins: I have no idea if this apache will be suitable for your
>purposes, but it is at least a static build and I've been using Apache
>servers built this way for several years with never so much as an oops.
>attached_file is just three lines:
>when you get more comfortable with it, you can start to make more
>complicated versions of it. When I want to archive a server build,
>all I keep is this file and the tarballs.