tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Lacson" <plac...@ibuyline.com>
Subject RE: Tomcat vs JSERV
Date Fri, 02 Jun 2000 19:28:23 GMT
I don't know if this will help but I had the exact same problem but on
Linux.

It happened on Suse 6.3 and Redhat 6.1 both running Apache 1.3.12
Suse was using Kernel 2.3.99-pre8 and Redhat was running Kernel 2.2.12-20
(not that this matters ;) I actually did have problems with the shared
memory in 2.3.99-pre8 but it was fixed when I added the /var/shm !!)

anyway..

I found that the I had to reconfigure my apache installation.  I got this
same mod_jserv compilation error when I configured my apache using the
following:

./configure --prefix=/path/to/my/apache --enable-rule=SHARED_CORE

The problem was that I didn't run configure that enabled the particular
module *so* -- so to correct the problem I ran:

./configure --prefix=/path/to/my/apache --enable-rule=SHARED_CORE  --enable-
module=so

I then ran make, make install as usual.

I then ran the

/path/to/apache/bin/apxs -c -o mod_jserv.so *.c

in the jarkarta-tomcat source directory
/jakarta-tomcat/src/native/apache/jserv ****

!!! Before compiling I removed the jserv_wrapper_win.c from the directory
!!!

The compilation when fine after these steps..

Hope this helps..

-Patrick

-----Original Message-----
From: Anthony Quon [mailto:quon@iscp.telcordia.com]
Sent: Friday, June 02, 2000 8:39 AM
To: tomcat-user@jakarta.apache.org
Subject: Re: Tomcat vs JSERV


Fred,
 I am also having problems with compiling the JSERV module (mod_jserv.so)
that came with the Tomcat distribution. The compilation seems to go fine up
until the end:

zeus:/wow/quon/download/jakarta/jakarta-tomcat/src/native/apache/jserv#
perl5 /usr/HTTPServer/bin/apxs -c -o mod_jserv.so *.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c autochange.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_ajpv11.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_ajpv12.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_balance.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_image.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_mmap.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_protocols.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_status.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_utils.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_watchdog.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_wrapper.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_wrapper_unix.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c jserv_wrapper_win.c
gcc -DAIX=43 -U__STR__ -DAIX_BIND_PROCESSOR -DUSE_HSREGEX  -I/usr/HTTPServer
/include  -c mod_jserv.c
  -o mod_jserv.so mod_jserv.o jserv_wrapper_win.o jserv_wrapper_unix.o
jserv_wrapper.o jserv_watchdog.o jserv_utils.o jserv_status.o
jserv_protocols.o jserv_mmap.o jserv_image.o jserv_balance.o jserv_ajpv12.o
jserv_ajpv11.o autochange.o
apxs:Break: Command failed with rc=16711680

Same output for xlC as well....possible this can help some folks out that
are playing with JSERV module compilation.

Anthony

----- Original Message -----
From: "Fred Nenad Brkich" <fred@cs.rmit.edu.au>
To: <tomcat-user@jakarta.apache.org>
Sent: Friday, June 02, 2000 12:22 AM
Subject: Re: Tomcat vs JSERV


> Hi,
>
> > RE: Supported MIME types...I've been using JSERV for quite some time now
=
> > and have recently decided to go to tomcat to handle our servlets. The =
> > main reason for this move was to be able to use JDK 1.2.2 on AIX which =
> > did not work correctly for JSERV and I don't believe JSERV even =
> > officially supports 1.2.x. Now, I'm curious is going to Tomcat the best
=
> > way?
>
> Just to add my penneth-worth. I note that over the last few weeks
> a number of people, including myself, have posted a problem that
> indicated that the apxs script failed in building mod_jserv.so. As
> far as I am aware no-one provided an accurate or even partially
> helpful response. Why? Seems a lot of people were hitting the same
> dead-end, but nothing came back from the developers or the community.
> Add to this the complete lack of commercial support (so far as I
> am aware) for the Apache-Tomcat product; the almost total lack of
> worthwhile documentation for installation (eg on OS's such as
> HPUX11); and so on, and it becomes very difficult to recommend
> Apache-Tomcat as anything but a toy for part-time hackers.
>
> A much better way for you would be to get Apache-Lutris/Enhydra,
> which does come with some commercial support, and is a cool product.
>
> ;)
> Regards
> Fred
>
>
> --------------------------------------------------------------------------
> To unsubscribe, email: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commmands, email: tomcat-user-help@jakarta.apache.org
>


--------------------------------------------------------------------------
To unsubscribe, email: tomcat-user-unsubscribe@jakarta.apache.org
For additional commmands, email: tomcat-user-help@jakarta.apache.org


Mime
View raw message