Peter,
I think that we should stay a couple of versions behind with the JDK, so
that other operating systems (other than Solaris, Windows and Linux) have an
equivalent JDK version. The Java code is more likely to be platform
independent then.
I will have a look at the last release of the 1.4.1 line, I think this was
1.4.1_06.
Steve.
-----Original Message-----
From: Peter W. Draper [mailto:[log in to unmask]]
Sent: 05 December 2003 09:53
To: [log in to unmask]
Subject: Re: Which JDK?
On Thu, 4 Dec 2003, Alasdair Allan wrote:
> Right, I'm trying to rebuild everything from a clean checkout from CVS.
>
> I get the following on build,
>
> .
> .
> .
> get_ast_source:
> [mkdir] Created dir: /work/starlink/java/source/jniast/build/ast
> [untar] Expanding:
/work/starlink/java/source/jniast/src/ast/ast_source.tar into
/work/starlink/java/source/jniast/build/ast
>
> assemble_java:
> [mkdir] Created dir: /work/starlink/java/source/jniast/build/java
> [copy] Copying 21 files to
/work/starlink/java/source/jniast/build/java
>
> An unexpected exception has been detected in native code outside the VM.
> Unexpected Signal : 11 occurred at PC=0x40036EA1
Function=(null)+0x40036EA1
> Library=/lib/libpthread.so.0
>
> NOTE: We are unable to locate the function name symbol for the error
> just occurred. Please refer to release documentation for possible
> reason and solutions.
>
>
> Current Java thread:
> at java.lang.Object.wait(Native Method)
> - waiting on <0x442e0100> (a java.lang.UNIXProcess$Gate)
> at java.lang.Object.wait(Object.java:426)
> at java.lang.UNIXProcess$Gate.waitForExit(UNIXProcess.java:66)
> - locked <0x442e0100> (a java.lang.UNIXProcess$Gate)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:140)
> at java.lang.Runtime.execInternal(Native Method)
> at java.lang.Runtime.exec(Runtime.java:566)
> .
> .
> .
>
> in other words, it won't build on my machine any more, I'm running RH7.3
> with JDK 1.4.0_01 (this being what I have in /stardev).
>
> Is the system supposed to build for this combination? If not, what I'm
> supposed to have to actually build the software these days?
Hi Al,
does look a bit knackered. I use RH9 and 1.4.1_02 or 1.4.2_02 and they are
OK, but there is no known reason why your combination shouldn't work too,
but crashing in the thread library is a classic OS incompatibility sign,
so update to 1.4.1 (seems to be the current favourite).
Cheers,
Peter.
|