tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Eggers <its_toas...@yahoo.com>
Subject Re: Binary of mod_jk.so for Apache 2.2.x
Date Thu, 14 Jul 2011 20:21:46 GMT
----- Original Message -----

> From: Christopher Schultz <chris@christopherschultz.net>
> To: Tomcat Users List <users@tomcat.apache.org>
> Cc: 
> Sent: Thursday, July 14, 2011 11:36 AM
> Subject: Re: Binary of mod_jk.so for Apache 2.2.x
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Jonathan,
> 
> On 7/14/2011 1:08 PM, Leffingwell, Jonathan R CTR FRCSE, JAX 7.2.2 wrote:
>>  Chris, something DID just dawn on me...
>> 
>>  I have my own account on that Linux server, though not with root 
>>  access or anything. Would it be possible for me to compile mod_jk.so 
>>  into my own space and then tell him where the mod_jk.so is?
> 
> Yes.
> 
>>  If so, would the following steps be how I would generate mod_jk.so 
>>  (and forgive the "newbie"ness of the question, please)?
>> 
>>  tar -xvzf tomcat-connectors-1.2.30-src.tar.gz
>> 
>>  cd tomcat-connectors-1.2.30-src/native/ # which apxs
> 
> The "# which apxs" was intended to be a command to determine the
> location of Apache httpd's "apxs" program, which is a
> configuration-dumping utility to help with building Apache httpd
> modules. apxs if often found in /usr/sbin/apxs so Leon's post was using
> that as an example:
> 
>>  ./configure --with-apxs=/usr/sbin/apxs --enable-api-compatibility
> 
> Replace /usr/sbin/apxs with whatever the result of "which apxs" is. If
> that doesn't return anything, you may have to have your SA install the
> Apache httpd development package or something. It might also be called
> "apxs2" (that's the case in my Debian Lenny environment).
> 
> Good luck,
> - -chris
>

An addendum concerning building mod_jk on a RedHat based system:

RedHat often (always?) splits libraries from their associated include files and development
resources. It really doesn't save a lot of space, so I guess the only reason is to create
a clean production (read, can't build software here) environment.

In order to build mod_jk on Fedora (and probably CentOS, RedHat EL), you'll need to have the
following installed (plus the normal development tools).

httpd-devel (provides /usr/sbin/apxs
apr-devel (provides the appropriate include files)
apr (required by apr-devel)
apr-util-devel (required by httpd-devel)
apr-util (required by apr-util)

There are other requirements buried in the list above, but if your admin installed these yum
should pull in the requirements.

It's good to have a development system that mirrors the software versions running on the production
system, with the addition of all the development libraries and tools.

. . . . just my two cents.

/mde/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message