There are two threads that split off from my original...

Thread one is mainly to you about me not being able to compile mod_jk.so
using the instructions on your site.

Thread two is mainly to Adrian regarding attempting use of the mod_jk.so
binary downloaded from jakarta.  (This thread also had a bit of a tangent
into my failures following the instructions on
http://www.pubbitch.org/jboss/mod_jk2.html trying to build mod_jk2.so)

Both threads end in tears of frustration and I know there's a root cause to
all of it. :(

Here I will paste the bulk of the email I have regarding Thread one mainly
to you regarding your how-to.

 ---

Following the instructions for mod_jk on your how-to and
'src/jk/native/BUILDING', I run:

  ./configure --with-apxs=/usr/local/apache2/bin/apxs

Which creates the Makefile environment...

I attempt the buildconf.sh script even though it isn't required and it fails
with the following:

libtoolize --force --automake --copy
aclocal
automake -a --foreign -i --copy
configure.in: 22: required file `scripts/build/unix/ltconfig' not found
autoconf
configure.in:24: AC_PROG_CPP was called before AC_PROG_CC

I try 'make' and, while it doesn't give an error, I get no mod_jk.so file
and the following messages:

Making all in common
make[1]: Entering directory `/path/to/src/jk/native/common'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/path/to/src/jk/native/common'
Making all in apache-2.0
make[1]: Entering directory `/path/to/src/jk/native/apache-2.0'
/bin/bash /usr/local/apache2/build/libtool --silent --mode=install cp
mod_jk.la `pwd`/mod_jk.so
libtool: install: warning: remember to run `libtool --finish
/usr/local/apache2/modules'
make[1]: Leaving directory `/path/to/src/jk/native/apache-2.0'

This leaves me with a mod_jk.la file that is 617 bytes. :(

[ j o h n ]

-----Original Message-----
From: Turner, John [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 2:53 PM
To: 'Tomcat Users List'
Subject: RE: mod_jk tomcat/apache connector issue



I'm stumped.  You're getting this error with the mod_jk.so file from the
Jakarta site?  OR an old one from my site?

John

> -----Original Message-----
> From: John Bullock [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 07, 2003 3:45 PM
> To: 'Tomcat Users List'
> Subject: RE: mod_jk tomcat/apache connector issue
>
>
> > > Everything looks fine with ld.so.1
> > >
> > > # echo $LD_LIBRARY_PATH
> > > /usr/local/lib:/usr/dt/lib:/usr/openwin/lib:/usr/lib
>
> -----Original Message-----
> From: Turner, John [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 07, 2003 2:40 PM
> To: 'Tomcat Users List'
> Subject: RE: mod_jk tomcat/apache connector issue
>
>
>
> Ooops, my bad.  Sorry about that.  What's the value of
> LD_LIBRARY_PATH in
> your environment?
>
> John
>
> > -----Original Message-----
> > From: John Bullock [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 07, 2003 3:39 PM
> > To: 'Tomcat Users List'
> > Subject: RE: mod_jk tomcat/apache connector issue
> >
> >
> > ldconfig is a linux-based configurable run-time linking
> system, right?
> >
> > I'm on Solaris 8 (which is coincidentally how I found your how-to)
> >
> > The solaris equivalent is.. crle it looks like although I'm
> > not sure how it
> > is used.
> >
> > Versions:
> > Solaris 8
> > gcc 2.95.3
> > libtool 1.4
> > tar 1.13.19
> > tomcat connectors source 4.1.18
> > etc. (let me know if you need any more versions for make,
> > autoconf, etc.)
> >
> > [ j o h n ]
> >
> > -----Original Message-----
> > From: Turner, John [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 07, 2003 2:04 PM
> > To: 'Tomcat Users List'
> > Subject: RE: mod_jk tomcat/apache connector issue
> >
> >
> >
> > Have you run ldconfig lately?  I think it is supposed to run
> > on startup, but
> > maybe something got munged up recently.
> >
> > John
> >
> >
> >
> > > -----Original Message-----
> > > From: John Bullock [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, January 07, 2003 3:03 PM
> > > To: 'Tomcat Users List'
> > > Subject: RE: mod_jk tomcat/apache connector issue
> > >
> > >
> > > Everything looks fine with ld.so.1
> > >
> > > # echo $LD_LIBRARY_PATH
> > > /usr/local/lib:/usr/dt/lib:/usr/openwin/lib:/usr/lib
> > >
> > > # find . | grep ld.so
> > > ./usr/lib/sparcv9/librtld.so.1
> > > ./usr/lib/sparcv9/ld.so.1
> > > ./usr/lib/sparcv9/libld.so.2
> > > ./usr/lib/sparcv9/libld.so.3
> > > ./usr/lib/ld.so
> > > ./usr/lib/ld.so.1
> > > ./usr/lib/librtld.so.1
> > > ./usr/lib/mdb/kvm/krtld.so
> > > ./usr/lib/mdb/kvm/sparcv9/krtld.so
> > > ./usr/lib/libld.so.2
> > > ./usr/lib/libld.so.3
> > >
> > > *sigh*... I was hoping that was it.  Seems like every time
> > I run into
> > > something wacky, it has to do with libraries and LD_LIBRARY_PATH
> > >
> > > [ j o h n ]
> > >

--
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]>

Reply via email to