Jerry, I've never tried building mod_jk from source as the files always existed on the Jakarta website. Although I don't see it here, are you looking to perform a "customized" compile? If not, is there another reason to compile from source instead of using the binaries? I've never had any problems getting mod_jk to work--just DBCP and that was because of a stupid typo on my part.
Sincerely, Pantek Incorporated Justin L. Spies URI: http://www.pantek.com Ph 440.519.1802 Fax 440.248.5274 Cell 440.336.3317 -----Original Message----- From: Jerry Ford [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 8:57 PM To: Tomcat Users List Subject: mod_jk...again When I try to build mod_jk from the source contained in jakarta-tomcat-connectors-4.1.12-src.tar, the process breaks before it gets started. I am following the instructions on John Turner's how-to page, but when I run the configure script, it breaks at ltconfig---I get an error message that says a host type must be specified when the --no-verify flag is used. But running ltconfig --help shows no parameter for specifying host type, and the command is run from the configure script anyway. Can anyone tell me what's going on, and more importantly how do I correct it? Here's the output when I run configure; the path to apxs is correct, and JAVA_HOME points to a valid Java 1.4 JDK: [jford@gizmo native]$ ./configure --with-apxs=../../../apache_1.3.27/bin/apxs --with-java-home=$JAVA_HOME checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets $(MAKE)... yes checking for working aclocal... found checking for working autoconf... found checking for working automake... found checking for working autoheader... found checking for working makeinfo... found checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for ranlib... ranlib checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for ld used by GCC... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed [jford@gizmo native]$ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
