>Number: 4219 >Category: general >Synopsis: JServ1.0b3 does not build: only compiles Hello.java >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Apr 9 17:20:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.0b3 >Environment: Linux RedHat 5.2 Linux peerless.cs.utah.edu 2.2.3 #6 SMP Sun Mar 21 19:58:18 MST 1999 i686 unknown >Description: This is in reference to my previous report about configure not telling me anything. So I've figured out that the "/path/to/apache/installation" is the output apxs -q PREFIX, which is
> echo `apxs -q PREFIX` /usr Fine, so I guess giving --with-apache-dir doesn't help. Here is the output of make: [EMAIL PROTECTED] [72](/opt/Apache-JServ-1.0b3) > make Making all in src make[1]: Entering directory `/opt/Apache-JServ-1.0b3/src' Making all in c make[2]: Entering directory `/opt/Apache-JServ-1.0b3/src/c' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/opt/Apache-JServ-1.0b3/src/c' Making all in java make[2]: Entering directory `/opt/Apache-JServ-1.0b3/src/java' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/opt/Apache-JServ-1.0b3/src/java' make[1]: Leaving directory `/opt/Apache-JServ-1.0b3/src' Making all in docs make[1]: Entering directory `/opt/Apache-JServ-1.0b3/docs' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/opt/Apache-JServ-1.0b3/docs' Making all in example make[1]: Entering directory `/opt/Apache-JServ-1.0b3/example' CLASSPATH=/x/gback/classes/jsdk.jar:$CLASSPATH /x/gback/transvirtual/install-plain/bin/javac Hello.java And that's it. >How-To-Repeat: Simply configure and make, like so ./configure --with-jsdk=... make >Fix: No, I don't. Probably an automake problem. I guess now I'll have to dig through Makefiles, then Makefile.ins, then Makefile.am to figure out why it isn't doing anything... Isn't automake great? >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [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! ]