Hello Rainer, First, that for all the help..
The examples I gave are from the make. The confusing part is some docs just show doing the configure, make, copy the mod, make clean on the Apache site docs. I have also seem some docs show doing configure, make, make install, copy the mod, make clean. I am not sure if I need the make install? > Exactly, more precisely, if there is already an mod_jk.so in the .libs, > that's actually the final result of the build process, and you can put > it into every directory you like to install it. To really use it, you > have to give it's path name in the LoadModule httpd directive. mod_jk.so.0 is trying to be renamed from the apache-1.3 directory when it resides in the apache-1.3/.libs directory. I did a file command on the mod_jk.so.0 file in .libs and it shows >pwd /software/source/gnu/apache_tomcat/work/tomcat-connectors-1.2.25-src/native/apac he-1.3/.libs > file mod_jk.so.0 mod_jk.so.0: executable (RISC System/6000) or object module not stripped So am I thinking I can do the copy/rename myself to Apache Web Server and rename it to mod_jk.so under some directory. That is if I don't need to do make install after the make. > Ah, OK: for httpd 1.3 the directory is libexec, not modules. It has > exactly the same purpose. As noted above, you can put the file in any > place you like, as long as the LoadModule contains the path name. > Convention is a sub directory libexec for httpd 1.3 and modules for 2.x > below the ServerRoot of httpd. I see what your saying about pointing to it in the Apache httpd.conf file. Just as long as it is found. LoadModule jk_module modules/mod_jk.so Thank you very much. Rich
