Building JServ
Having created gmake
, move to
the mod_jserv source
directory. Before you start, you need to have compiled Apache so that
JServ can pass its configure checks. If you have got this far in the
book, you probably will already have compiled Apache once or twice,
but if not — now is a good time to start. Go to Chapter 1.
You then need to decide whether you want to build it into the Apache executable (recommended) or prepare it as a DSO. We took the first route and configured mod_jserv with this:
MAKE=/usr/local/bin/gmake ./configure --prefix=/usr/local --with-apache-src=/usr/src/ apache/apache_1.3.19 --with-jdk-home=/usr/src/java/jdk1.1.8 --with-JSDK=/usr/src/ jsdk/JSDK2.0/lib
Your paths in general will be different. --prefix
invokes the location where you want the JServ bits to be put. Rather
perversely, they appear in the subdirectory .../etc
below the directory you specify. You might also think that
you were required to put /src
on the end of the
Apache path, but you’re not. If the process fails
for any reason, take care to delete the file config.cache
before you try again. You might want to write the
necessary commands as a script since it is unlikely to work at the
first attempt:
rm config.cache MAKE=/usr/local/bin/gmake ./configure --prefix=/usr/local/bin --with-apache-src=/usr/src/ apache/apache_1.3.19 --with-jdk-home=/usr/src/java/jdk1.1.8 --with-JSDK=/usr/src/ jsdk/JSDK2.0/lib > log
If you use mod_ssl, you should add
--enable-EAPI
. The script’s voluminous comments ...
Get Apache: The Definitive Guide, 3rd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.