There is no "apxs" on the Linux server. The S.A. confirmed this. That =
file and nothing closely resembling it are found anywhere on the whole =
box. Is it needed to compile mod_jk?
-----Original Message-----
From: Mark Eggers [mailto:its_toasted@yahoo.com]=20
Sent: Thursday, July 14, 2011 1:22 PM
To: Tomcat Users List
Subject: Re: Binary of mod_jk.so for Apache 2.2.x
----- Original Message -----
> From: "Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2" =
<jonathan.leffingwell.ctr@navy.mil>
> To: Tomcat Users List <users@tomcat.apache.org>
> Cc:=20
> Sent: Thursday, July 14, 2011 10:08 AM
> Subject: RE: Binary of mod_jk.so for Apache 2.2.x
>=20
> Chris, something DID just dawn on me...
>=20
> I have my own account on that Linux server, though not with root =
access or=20
> anything.=A0 Would it be possible for me to compile mod_jk.so into my =
own space=20
> and then tell him where the mod_jk.so is?=A0 If so, would the =
following steps be=20
> how I would generate mod_jk.so (and forgive the "newbie"ness of the=20
> question, please)?
>=20
> tar -xvzf tomcat-connectors-1.2.30-src.tar.gz
>=20
> cd tomcat-connectors-1.2.30-src/native/ # which apxs=20
>=20
> ./configure --with-apxs=3D/usr/sbin/apxs --enable-api-compatibility=20
>=20
> make=20
>=20
> make install
>=20
>=20
> At this point, I think all I want to do is produce a functioning =
mod_jk.so and=20
> let him put it into the modules directory.=A0 Would this do it?
>=20
> Thanks again!
>=20
> JL
>=20
>=20
> -----Original Message-----
> From: Christopher Schultz [mailto:chris@christopherschultz.net]=20
> Sent: Thursday, July 14, 2011 12:34 PM
> To: Tomcat Users List
> Subject: Re: Binary of mod_jk.so for Apache 2.2.x
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Leon,
>=20
> On 7/12/2011 7:42 PM, Leon Kolchinsky wrote:
>> Go to http://tomcat.apache.org/download-connectors.cgi and download
>> the source code:
>>=20
>> # tar -xvzf tomcat-connectors-1.2.30-src.tar.gz
>>=20
>> Read docs/webserver_howto/apache.html or native/BUILDING.txt for
>> options.
>>=20
>> # cd tomcat-connectors-1.2.30-src/native/ # which apxs # ./configure
>> --with-apxs=3D/usr/sbin/apxs --enable-api-compatibility # make # =
make
>> install
>=20
> All that as root? Hmm.
>=20
> Also, not everyone has a C compiler, especially on a production =
machine.
> (The answer, of course, is to build somewhere else and upload.)
>=20
> Jonathan, I understand that you want convenience, but there are =
several
> factors to consider, here:
>=20
> 1. Unless you download a binary from a trusted source (i.e. not anyone
> =A0 on this list, but something like something.apache.org, or from =
your
> =A0 distro's package manager), you should consider yourself =
compromised.
>=20
> 2. If you build your own mod_jk, you know it will work with your exact
> =A0 environment. No weird problems with slight version mismatches =
between
> =A0 httpd version or other libraries. No questions about which
> =A0 architecture's files you need to download, etc.
>=20
> 3. Building mod_jk from source is relatively trivial. See above. Most
> =A0 Linux distros some with a C compiler by default, and all of them
> =A0 can trivially install gcc.
>=20
> Consider trying it.
>=20
> Recently, the Tomcat team decided to stop providing binaries for *NIX
> platforms because of the above (maybe that was just for tcnative, but =
I
> wouldn't be surprised if the policy is now to avoid rolling binaries =
for
> any non-Java components).
>=20
> Why? Because if we wanted to provide binaries for, say, mod_jk, we =
need
> to support (at least) two architectures: x86 and x86_64. Also, there =
are
> 4 major versions of Apache httpd: 1.3, 2.0, 2.2, and 2.4. Sometimes,
> even httpd patch level can affect compatibility (though it really
> shouldn't) or maybe it was built against 2.2.11 but the user has =
2.2.13
> and wants to know "why no binary?".
>=20
> We cannot possibly provide enough binaries to make everyone happy. =
Since
> it's so easy to build mod_jk, we ask users in *NIX environments to =
just
> do it.
>=20
> We do provide binaries for both 32- and 64-bit Microsoft Windows
> environments for Apache httpd, Microsoft IIS and (wtf?) Netscape,
> because those folks rarely have compilers handy.
>=20
> If you have any trouble building mod_jk, please don't hesitate to come
> back for help.
>=20
> - -chris
If all the tools are available on the production system (compiler, =
libraries), then you do this as a normal user:
myuser$ tar -xvzf tomcat-connectors-1.2.32-src.tar.gz
myuser$=A0cd tomcat-connectors-1.2.32-src/native/
myuser$=A0which apxs=A0=A0
myuser$=A0./configure --with-apxs=3D/usr/sbin/apxs =
--enable-api-compatibility=A0
myuser$=A0make=A0
(where=A0myuser$ is whatever prompt you have for your user id).
Then you tell the system admin where the location is (probably now in =
/home/myuser/tomcat-connectors-1.2.32-src/native/), and have him do as =
root:
# cd=A0/home/myuser/tomcat-connectors-1.2.32-src/native/
# make install
That should get the mod_jk.so installed. The administrator will then =
have to configure it (see=A0tomcat-connectors-1.2.32-src/conf for =
examples), and finally restart the Apache HTPPD server.
Hopefully the administrator should be able to do that.
. . . . just my two cents
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
|