mod_jserv/4574: mod_jserv.so fails to build. Java JServ modules build and install fine.

[Matt Pickering <ma...@speedskater.com>]

>Number:         4574
>Category:       mod_jserv
>Synopsis:       mod_jserv.so fails to build.  Java JServ modules build and install fine.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Jun 12 17:50:01 PDT 1999
>Last-Modified:
>Originator:     mattp@speedskater.com
>Organization:
apache
>Release:        1.3
>Environment:
Redhat Linux 2.0.36
GNU C
Default Apache installation
>Description:
Run configure using a default set of options causes the Java JServ modules to build
and install but the mod_jserv module fails to build with an error:

Make:  nothing to do for 'all' in src/c

I am using a default Redhat 5.2 installation with no patches or updates other 
than those shipped with the standard CD.  Apache 1.3.3 was installed by Redhat 
into a default set of directories and is running fine.  The JAVA_HOME and 
JSDK_HOME variables are set and the Java compiler is working fine.  

Java compiler and VM is Blackdown JDK1.1.6v2.  Very stable.

>How-To-Repeat:
Run ./configure after unpacking the tar file on a standard Redhat system with
no options and then run make.
>Fix:
No suggestions, as tracing the Makefiles is giving me a headache.  I have seen
many problem reports related to this and I *need* to run JServ on my Apache 
server.  I would settle for a simple manual Makefile that *works*.

Could a developer please look into this or at least provide the necessary 
include and build parameters for GCC so I can build the modules by hand and 
instructions to move them manually into their proper locations.

Any help on this is greatly appreciated, as I am sure there are many others 
with the same problem who just want a product that works right.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]