On 25.09.2009 15:46, Strickland, Lawrence P wrote:
> I ran the find commands and did not find any of these files. I ran the
> build with the new tools and this is what I got.
> 
> Could this one be my shared object module?
> 180225 1053 -rw-r--r--  1 root      system     1077292 Sep 25 08:40
> ./native/apache-2.0/.libs/libmod_jk.a

Yes, this could be it. It could either be a static library (not good) or
a shared library (good). Most platforms use *.a for static libs, but I
vaguely remember that AIX used it for shared.

You could try "file native/apache-2.0/.libs/libmod_jk.a" to see what AIX
says which type of file it is.

Did you try loading it into the web server with LoadModule?

For the build, did you use the new tarball and additionally the fixed
libtool, or only the new tarball?

Regards,

Rainer

> bash-3.00# pwd
> /home/strickll/tomcat-connectors-1.2.28-new_autotools-src
> bash-3.00# find . -name \*mod_jk\* -ls
> 176652  109 -rw-------  1 51       develope    111577 Mar 19  2009
> ./native/apache-1.3/mod_jk.c
> 176653    8 -rw-------  1 51       develope      7824 Jun 17  2007
> ./native/apache-1.3/mod_jk.dsp
> 176655    1 -rw-------  1 51       develope        11 Sep  6  2002
> ./native/apache-1.3/mod_jk.exp
> 177030  126 -rw-------  1 51       develope    128597 Mar 19  2009
> ./native/apache-2.0/mod_jk.c
> 177031    8 -rw-------  1 51       develope      7757 Jun 17  2007
> ./native/apache-2.0/mod_jk.dsp
> 180225 1053 -rw-r--r--  1 root      system     1077292 Sep 25 08:40
> ./native/apache-2.0/.libs/libmod_jk.a
> 180226    1 -rw-r--r--  1 root      system         756 Sep 25 08:40
> ./native/apache-2.0/.libs/mod_jk.lai
> 180227    1 lrwxrwxrwx  1 root      system          12 Sep 25 08:40
> ./native/apache-2.0/.libs/mod_jk.la -> ../mod_jk.la
> 177054    1 -rw-r--r--  1 root      system         765 Sep 25 08:17
> ./native/apache-2.0/mod_jk.la.
> 177077 1053 -rw-r--r--  1 root      system     1077292 Sep 25 08:40
> ./native/apache-2.0/libmod_jk.a
> 177073  155 -rw-r--r--  1 root      system      158506 Sep 25 08:40
> ./native/apache-2.0/mod_jk.o
> 177072    1 -rw-r--r--  1 root      system         297 Sep 25 08:40
> ./native/apache-2.0/mod_jk.lo
> 177074    1 -rw-r--r--  1 root      system         756 Sep 25 08:40
> ./native/apache-2.0/mod_jk.la
> bash-3.00# ./buildconf.sh
> bash-3.00# pwd
> bash-3.00#
> 
> -----Original Message-----
> From: Rainer Jung [mailto:rainer.j...@kippdata.de] 
> Sent: Thursday, September 24, 2009 6:06 PM
> To: Tomcat Users List
> Subject: Re: Has anyone been successful building mod_jk on AIX 6.1 ?
> 
> On 25.09.2009 00:55, Strickland, Lawrence P wrote:
>> If the shared object module in not called mod_jk.so then what is it
> called? Is it mod_jk.o?
>> And, if that is the case where does it need to be? In the
> apache/modules directory?
> 
> See the below find command. It could be mod_jk.so, mod_jk.a or
> mod_jk.so.0. But please note what I also wrote below. If you use the
> standard src download, even if the build works, it might not be a really
> good binary, because the platform detection doesn't work with the old
> config.guess and configure.
> 
> And yes: once you've got a good shared object file for AIX, you can put
> it into the modules folder of httpd. Actually you can put it anywhere
> you like, but if you use the relative path modules/... in the LoadModule
> directive, then it has to be in the modules directory of httpd.
> 
> Regards,
> 
> Rainer
> 
> ________________________________
>>
>> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
>> Sent: Thu 9/24/2009 4:24 PM
>> To: Tomcat Users List
>> Subject: Re: Has anyone been successful building mod_jk on AIX 6.1 ?
>>
>>
>>
>> Hi Lawrence,
>>
>> On 24.09.2009 22:48, Strickland, Lawrence P wrote:
>>> This is the output of my build run.
>>> So apparently I am building version 1.2.28 with XLC 10.1 and Apache
>>> 2.2.13
>>>
>>> #./httpd -v
>>> Server version: Apache/2.2.13 (Unix)
>>> Server built:   Sep 22 2009 13:27:47
>>>
>>> # gmake -v
>>> GNU Make 3.80
>>>
>>> /home/strickll/tomcat-connectors-1.2.28-src/native
>>>
>>> bash-3.00# CC="cc_r -qlanglvl=extc89" ./configure
>>> --with-apxs=/usr/local/apache2/bin/apxs
>>
>> ...
>>
>> Do the following commands find a build result:
>>
>> find /home/strickll/tomcat-connectors-1.2.28-src -name "mod_jk.a" -ls
>>
>> find /home/strickll/tomcat-connectors-1.2.28-src -name "mod_jk.so.*"
> -ls
>>
>> I once did build for AIX but using an own toolchain based on gcc. One
> of
>> the things I had to fix, was that config.guess (and also configure
> etc.)
>> was to old to detect AIX 6. I checked 1.2.28 and unfortunately we
> didn't
>> use the updated autotools when doing the release. I ran buildconf.sh
>> once more with newer autotools, so you might want to check whether the
>> archive at
>>
>>
> http://people.apache.org/~rjung/mod_jk-dev/source/jk-1.2.28-aix/tomcat-c
> onnectors-1.2.28-new_autotools-src.tar.gz
>>
>> works better for you.
>>
>> But I vaguely also remember that there was also a problem with
> libtool.
>> I don't really remember precisely, but on AIX it wanted to build
> shared
>> libs as .a file instead of .so. It worked when applying the following
>> ksh snipppet:
>>
>>
>>       for f in `find . -type f -name libtool`
>>       do
>>          echo "Fixing $f..."
>>          cp -p $f $f.aix_orig
>>          sed -e 's#hardcode_action=immediate#hardcode_action=relink#'
> \
>>              -e 's#hardcode_direct=yes#hardcode_direct=no#' \
>>              -e 's#hardcode_minus_L=no#hardcode_minus_L=yes#' \
>>              $f.aix_orig > $f
>>       done
>>
>> but maybe you won't need it using XLC.
>>
>> Concerning "make install": don't really use it. You can copy over the
>> mod_jk.so (or however the shared object file is called on AIX) to the
>> modules directory.
>>
>> Let us know your findings, so that we will at least ensure that we use
>> the right autotools for the future releases.
>>
>> Regards,
>>
>> Rainer

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

Reply via email to