Sorry friend, I dont have any clue on issue. I think you should also check what are your gcc, make, perl versions and if they are suggested versions to comple your jk.
My problem was with my 'make' version. It was a bit older and able to understand makefile grammer. Good luck. -----Original Message----- From: Graeme [mailto:[EMAIL PROTECTED] Sent: Monday, June 21, 2004 7:50 PM To: Tomcat Users List Subject: Re: mod_jk install problem Thank you to everyone who replied to my post. BK, I've got apache installed an running. The version I'm using is: Apache/2.0.40 Server I installed mod_jk from http://www.apache.org/dist/jakarta/tomcat-connectors/jk/ , the file I downloaded is: jakarta-tomcat-connectors-jk-1.2-src-current.tar.gz After doing ./configure --with-apxs=/usr/sbin/apxs I tried issuing the "make" command I got this: ../common/jk_ajp12_worker.lo ../common/jk_connect.lo ../common/jk_msg_buff.lo ../common/jk_util.lo ../common/jk_ajp13.lo ../common/jk_pool.lo ../common/jk_worker.lo ../common/jk_ajp13_worker.lo ../common/jk_lb_worker.lo ../common/jk_sockbuf.lo ../common/jk_map.lo ../common/jk_uri_worker_map.lo ../common/jk_ajp14.lo ../common/jk_ajp14_worker.lo ../common/jk_md5.lo ../common/jk_ajp_common.lo ../common/jk_context.lo i386-redhat-linux-gcc: ../common/jk_ajp12_worker.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_connect.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_msg_buff.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_util.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_ajp13.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_pool.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_worker.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_ajp13_worker.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_lb_worker.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_sockbuf.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_map.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_uri_worker_map.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_ajp14.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_ajp14_worker.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_md5.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_ajp_common.lo: No such file or directory i386-redhat-linux-gcc: ../common/jk_context.lo: No such file or directory make[1]: *** [mod_jk.la] Error 1 make[1]: Leaving directory `/usr/src/jakarta-tomcat-connectors-jk-1.2.5-src/jk/native/apache-2.0' make: *** [all-recursive] Error 1 [EMAIL PROTECTED] native]# As you will see in my initial post, these missing files appear to be in the "apache-2.0" directory. Do you think I should copy them to the directory it expects to find them and try issuing "make" again, or do something else? Cheers in advance, Graeme :) ----- Original Message ----- From: "Kommuru, Bhaskar" <[EMAIL PROTECTED]> To: "'Tomcat Users List'" <[EMAIL PROTECTED]> Sent: Monday, June 21, 2004 12:04 PM Subject: RE: mod_jk install problem > I have struggled/managed before to compile on solaris8. but not on Redhat9. > What is you mod_jk version? > I remember i have changed something like.. "apx" path .configure file as i > found it hardcoded there. I have specified the apx-path to apache > installation directory (usr/local/apache2/apxs). > Have you installed your apache as well? If so, what is the version? > Let me know, hope we can sort it out! > BK > > -----Original Message----- > From: Graeme [mailto:[EMAIL PROTECTED] > Sent: Sunday, June 20, 2004 7:45 PM > To: Tomcat Users List > Subject: mod_jk install problem > > > Afternoon all, I'm trying to install mod_jk and I can't create the mod_jk.so > file. I think the problem is something to do with: > > "need to check for Perl first, apxs depends on it...checking for perl... > /usr/bin/perl > Use of uninitialized value in concatenation (.) or string at /usr/sbin/apxs > line 262." > > I'm using Redhat 9. > > Anyone got any ideas? > > > [EMAIL PROTECTED] native]# ./configure --with-apxs=/usr/sbin/apxs > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking dependency style of gcc... none > checking for ld used by GCC... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking for a sed that does not truncate output... /bin/sed > checking whether ln -s works... yes > checking how to recognise dependent libraries... pass_all > checking command to parse /usr/bin/nm -B output... ok > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking for ranlib... ranlib > checking for strip... strip > checking for objdir... .libs > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.lo... yes > checking if gcc supports -fno-rtti -fno-exceptions... yes > checking whether the linker (/usr/bin/ld) supports shared libraries... yes > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking whether -lc should be explicitly linked in... no > creating libtool > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ANSI C... (cached) none needed > checking dependency style of gcc... (cached) none > checking for ld used by GCC... (cached) /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes > checking for test... /usr/bin/test > checking for rm... /bin/rm > checking for grep... /bin/grep > checking for echo... /bin/echo > checking for sed... /bin/sed > checking for cp... /bin/cp > checking for mkdir... /bin/mkdir > checking for libtool... /usr/bin/libtool > need to check for Perl first, apxs depends on it... > checking for perl... /usr/bin/perl > could not find /usr/sbin/apxs > configure: error: You must specify a valid --with-apxs path > [EMAIL PROTECTED] native]# vi /usr/sbin/apxs > [EMAIL PROTECTED] native]# ./configure --with-apxs=/usr/sbin/apxs > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ANSI C... none needed > checking dependency style of gcc... none > checking for ld used by GCC... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking for a sed that does not truncate output... /bin/sed > checking whether ln -s works... yes > checking how to recognise dependent libraries... pass_all > checking command to parse /usr/bin/nm -B output... ok > checking how to run the C preprocessor... gcc -E > checking for egrep... grep -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking for ranlib... ranlib > checking for strip... strip > checking for objdir... .libs > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.lo... yes > checking if gcc supports -fno-rtti -fno-exceptions... yes > checking whether the linker (/usr/bin/ld) supports shared libraries... yes > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking whether -lc should be explicitly linked in... no > creating libtool > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ANSI C... (cached) none needed > checking dependency style of gcc... (cached) none > checking for ld used by GCC... (cached) /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes > checking for test... /usr/bin/test > checking for rm... /bin/rm > checking for grep... /bin/grep > checking for echo... /bin/echo > checking for sed... /bin/sed > checking for cp... /bin/cp > checking for mkdir... /bin/mkdir > checking for libtool... /usr/bin/libtool > need to check for Perl first, apxs depends on it... > checking for perl... /usr/bin/perl > Use of uninitialized value in concatenation (.) or string at /usr/sbin/apxs > line 262. > building connector for "apache-2.0" > checking for target platform... unix > no apache given > configure: creating ./config.status > config.status: creating Makefile > config.status: creating apache-1.3/Makefile > config.status: creating apache-1.3/Makefile.apxs > config.status: creating apache-2.0/Makefile > config.status: creating apache-2.0/Makefile.apxs > config.status: creating common/Makefile > config.status: creating common/list.mk > config.status: creating jni/Makefile > config.status: executing depfiles commands > > [EMAIL PROTECTED] native]# ls > aclocal.m4 BUILDING config.status iis Makefile.am scripts > apache-1.3 build.xml configure isapi Makefile.in > apache-2.0 CHANGES.txt configure.in jni netscape > autom4te.cache common docs libtool nt_service > buildconf.sh config.log domino Makefile README > > [EMAIL PROTECTED] native]# cd apache-2.0/ > [EMAIL PROTECTED] apache-2.0]# ls > bldjk.qclsrc jk_ajp14_worker.o jk_md5.lo jk_util.o > config.m4 jk_ajp_common.lo jk_md5.o jk_worker.lo > jk_ajp12_worker.lo jk_ajp_common.o jk_msg_buff.lo jk_worker.o > jk_ajp12_worker.o jk_connect.lo jk_msg_buff.o Makefile > jk_ajp13.lo jk_connect.o jk_pool.lo Makefile.apxs > jk_ajp13.o jk_context.lo jk_pool.o > Makefile.apxs.in > jk_ajp13_worker.lo jk_context.o jk_sockbuf.lo Makefile.in > jk_ajp13_worker.o jk_lb_worker.lo jk_sockbuf.o mod_jk.c > jk_ajp14.lo jk_lb_worker.o jk_uri_worker_map.lo mod_jk.dsp > jk_ajp14.o jk_map.lo jk_uri_worker_map.o mod_jk.lo > jk_ajp14_worker.lo jk_map.o jk_util.lo mod_jk.o > [EMAIL PROTECTED] apache-2.0]# > > ____________________________________________________________________________ ______________________________________________________ > > For information about the Standard Bank group visit our web site <www.standardbank.co.za> > ____________________________________________________________________________ ______________________________________________________ > > Disclaimer and confidentiality note > Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. > It is confidential, legally privileged and protected by law. > Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. > The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, > disclose or use the content in any way. > Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. > ____________________________________________________________________________ _______________________________________________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________________________________________________________________________________________ For information about the Standard Bank group visit our web site <www.standardbank.co.za> __________________________________________________________________________________________________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ___________________________________________________________________________________________________________________________________
