PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : [RH9] mod_jk bauen.. bleibe hängen



dark_red
07.01.04, 10:19
hi

will mir gerade mod_jk bauen, doch ich bleibe bei ./configure hängen:


[root@nirvana native]# ./configure
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
no apxs given
checking for target platform... unix
no apache given
configure: error: Cannot find the WebServer


les ich da richtig? er findet den webserver nicht, obwohl ich den apache httpd schon beim redhat setup installiert habe :eek: ?

was soll ich nun tun? :(

Bauchi
07.01.04, 10:22
1.) nimm das fertige mod_jk von apache.org
http://ftp.leo.org/pub/comp/general/infosys/www/daemons/apache/dist/jakarta/tomcat-connectors/jk/binaries/
http://ftp.leo.org/pub/comp/general/infosys/www/daemons/apache/dist/jakarta/tomcat-connectors/jk2/binaries/
2.) installier das apache devel paket und gib dem configure den pfad zu apxs mit ...
-> ./configure --help sagt dir wie er das apxs erwartet (ich geh mal von --with-apxs=/pfad aus)
dann such nach apxs find / -name "apxs"

dark_red
07.01.04, 10:50
1) die scheinen wohl auch keine linux bins hinzubekommen... linuxordner sind da entweder nicht vorhanden oder sie sind leer... :eek:

2) danke. ./configure geht jetzt... aber nun mag make nicht mehr weiter :(



...
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] Fehler 1
make[1]: Verlassen des Verzeichnisses Verzeichnis »/usr/src/jakarta-tomcat-connectors-jk-1.2.5-src/jk/native/apache-2.0«
make: *** [all-recursive] Fehler