Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-dev@jakarta.apache.org
Sender: jfclere@vtxrm2.bcn.fsc.net
Message-ID: <3B01695A.56AC78CC@fujitsu-siemens.com>
Date: Tue, 15 May 2001 19:37:30 +0200
From: jean-frederic clere <jfrederic.clere@fujitsu-siemens.com>
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: configure for jakarta-tomcat-connectors
References: <Pine.LNX.4.21.0105150727230.1178-100000@simona.wyn.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

cmanolache@yahoo.com wrote:
> =

> Wow, it is so good to see development discussion on tomcat-dev, and be
> able to participate :-)
> =

> I have a big question - what happens if configure/libtool is used and
> different options are given for mod_jk and apache ?
> =

> I can't give a concrete example, but APXS had the big benefit that it
> "cached" all the decisions taken when Apache was built, and that insure=
d
> that the same decisions were used when building modules.

Using configure/libtool allows to find JAVA_HOME for jni. And will allow =
to
build a static mod_jk.
Of course if --with-apxs is used the configure/libtool should try to read=
 the
parameters from apxs or even use apxs instead libtool (even if I still do=
 not
know how to it right now!).

The first step (try) I have done uses APXS, configure is just used to fin=
d
whether to use apache-1.3 or apache-2.0.

By the way I have a question: Why jk_jni_worker.c is in common not in jni=
? What
it is used for? (I have to add JAVA_HOME to the configure for it and I am=

curious).
 =

> =

> I understand that most "guesses" done by configure will be the same - s=
o
> by doing configure again we'll likely get the same flags/options, but
> there are some options and some special features that could affect us i=
n
> very tricky ways.
> =

> You know all the trubles you get with KDE/Gnome when a certain binary i=
s
> linked against an older library - or the EAPI problems. It is possible
> to have multiple versions of a library on a system, or to have apache
>  configured to use a very specific version ( /usr/secure/libs/xxxx).
> =

> Costin
> =

> On Tue, 15 May 2001, jean-frederic clere wrote:
> =

> > GOMEZ Henri wrote:
> > >
> > > >I have started a configure.in and makefile(s).in for the
> > > >jakarta-tomcat-connectors.
> > > >Currently I have just prepared it for Apache2.0 and Apache1.3,
> > > >before going on I
> > > >have some questions:
> > >
> > > I tested the configure/makefile stuff and it works well but
> > > could you also add the java detection for JNI support ?
> > >
> > > ie: --with-java=3D/usr/jdk1.3.0/
> >
> > My idea is to build one connector per call of configure/make, --with-=
java should
> > build the JNI support, correct?
> > I have noted that common contains jk_jni_worker.c, should not we move=
 it in jni?
> >
> > >
> > > Many users asked about statically compiling mod_jk in Apache,
> > > could you add a --with-apache flag ?
> >
> > Yes, but we cannot use apxs for that... Following the ideas of mod_we=
bapp we
> > should libtool for this purpose.
> > Then it is more easy to use libtool for everything.
> >
> > >
> > > Do you think we could add also the config dir path to have
> > > default mod_jk.conf and workers.properties installed ?
> > >
> > > feature which could be added, is the config
> > >
> > > ie: --sysconfdir=3D/etc/httpd/conf        (=E0 la Redhat)
> >
> > If we use --with-apxs the conf is given by apxs, in case we use --wit=
h-apache
> > yes.
> > This means we need to support "make install".
> >
> > >
> > > Thanks for that contribution
> >
> > You are welcome
> >