-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------

Frank, please turn off your HTML email!!! ;-)

> 1. I still don't understand this one, but you might. No matter what I
> did with the "--with-jdk-home" and all the flavors thereof, the configure
> kept failing saying it could not find the java compiler. I could run the
> compiler within the same bash shell without problem. Then I ended up
> opening up permission on the JDK with "chmod a+rx" and all worked
> ok. Seems mysterious to me that I could use the compiler within a
> shell, but permissions caused a problem as the same user in the
> same shell when running configure.

Hmm...I have no idea at all. ;-(

What version of the JDK? What OS?

> 2. Under Solaris 7, the older version of "make" (I can't determine exactly
> what it is) failed with messages I have seen before when "gmake" fixed
> the problem, which it did.

Yep, you HAVE to use GNU make. This is documented in the INSTALL document.

> 3. I'm not sure if this is on purpose, but in the distribution the logfile in
> jserv.conf is set to "mod_jserv.log" but within jserv.properties it is
> "jserv.log" Like I said, I am not sure if these are intentionally two
different
> logs or not.

They are two differnt longs. One is for the C portion of Apache JServ and
the other is for the Java portion. You should NOT set them to be the same
value since two different processes will try to open and write to that file
at the same time. ie: create a mess. I will add some text that makes this
more clear.

> 4. I was unsure with "--with-apache-src=" if the path should include the
> "src" directory or not. I ended up guessing that "src" wasn't necessary,
> but was unsure. I like the wording "--with-jdk-home" because I am sure
> what that means.

All the examples in the INSTALL document point to the root apache src
directory. I will add some text to the INSTALL document to clarify this.

> 5. For some reason, I at first seemed blind to the fact that the jserv
> module had to be activated with "--apache-module=...". Somehow I
> kept skipping over that in the docs each time I read through to
> determine why jserv wasn't part of httpd.

Any ideas on how to make that more clear? Not only does Apache JServ, by
default, attempt to do that for you, it is also spelled out in the INSTALL
document about 2-3 times and when you actually type "make install" for
Apache JServ (although, there it is harder to find in all the make output).

> Thank you everyone for keeping Apache-Jserv progressing. Hats off
> to all of you developers!

thanks!

-jon


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to