try compiling with apxs directly. I had problems as well.
Something like this (from the jk/native/apache_1.3 directory):
apxs -Wc,-O3 -I ../common -I /usr/java/include \
-I /usr/java/include/solaris \
-c mod_jk.c ../common/*c
Then copy the mod_jk.so file to the libexec directory. You may have to
adjust your include directories for your system
Jonathan
> -----Original Message-----
> From: Thad Humphries [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 25, 2002 4:10 PM
> To: [EMAIL PROTECTED]
> Subject: building connectors for 4.1.12
>
>
> Why does building connectors have to be such a pain? It
> never seems to
> go smoothly for me...
>
> My current problem is the connectors from
> jakarta-tomcat-connectors-4.1.12-src.tar.gz, specifically mod_jk
> (I am running RedHat 6.2, Apache 2.0.40, and libtool 1.4.2)
>
> I run buildconf.sh:
>
> $ ./buildconf.sh
> libtoolize --force --automake --copy
> aclocal
> automake -a --foreign -i --copy
> automake: configure.in: installing `scripts/build/unix/install-sh'
> error while copying
>
> automake: configure.in: installing `scripts/build/unix/mkinstalldirs'
> error while copying
>
> automake: configure.in: installing `scripts/build/unix/missing'
> error while copying
>
> configure.in: 22: required file `scripts/build/unix/ltconfig'
> not found
> autoconf
>
> Like the BUILDING file says, ignore errors from automake but configure
> doesn't work:
>
> $ ./configure --with-apxs=/usr/local/apache2/bin/apxs
> 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 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
> scripts/build/unix/ltconfig: scripts/build/unix/ltconfig: No such file
> or directory
> configure: error: libtool configure failed
>
>
> I see in tomcat-dev that ltconfig and other files were
> removed from CVS
> as "excessive... since they are autogenerated"
> (http://www.mail-archive.com/[email protected]/msg
26834.html)
Exactly where are they autogenerated? What step do I need to add?
--
------------------------------------------------------------------------
Thad Humphries "...no religious test shall ever be required
Web Development Manager as a qualification to any office or public
Phone: 540/675-3015, x225 trust under the United States." -Article VI
--
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]>
