----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
on 10/21/99 1:50 PM, Steve Snodgrass <[EMAIL PROTECTED]> wrote:
> You know, I understand when you dismiss people who ask questions answered in
> the docs, or don't give any useful information, but it gets a little annoying
> to be dismissed when you provide a detailed bug report. Fortunately I had
> time to look into the problem further and have isolated the actual problems in
> the code.
Ok, I apologize, I should have been more correct. Something is screwed up
with your paths. ;-) I'm not dismissing you...I'm forcing you to go back and
find out exactly why it is failing. Obviously that is not a bad thing since
you replied with some helpful fixes. ;-) We both ended up at the same end
point, I just choose to pick the direction that would piss you off. I'm
sorry about that, it is just something that I'm unfortunately good at.
> In the configure script, it will definitely prefer Java 1.1 over Java 1.2 if
> both are installed under the same tree. This should be fixed. The fix is
> extremely simple:
Ok, this is something that I thought was already fixed, but maybe I only
fixed it in ECS or something. Thanks for the patch.
> The second problem is actually the one that Jean-Luc pointed out. The
> "save-install.sh" script in the conf subdirectory which is used to install the
> config files does not pay attention to the "install" command that configure
> selects and instead just tries to run whatever install executable is in your
> path. This fails miserably on Solaris if it ends up running /usr/sbin/install
> since it needs a BSD-compatible version of install. That script needs to be
> fixed to run the same install command that configure selects.
This is definitely already fixed in CVS. I had that same problem. The fix
was to have autoconf build the save-install.sh file.
> I suspect that there is still another bug lurking in configure that comes up
> with the wrong JAVA_PLATFORM when you manually specify JDK_HOME, but I don't
> really have the incentive to track that one down since the above patch allows
> configure to find the right JDK and platform itself.
Cool.
-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]
