Re: 3rd JDK for Linux/Intel available (OpenGroup)
Linux Weekly News <[EMAIL PROTECTED]> wrote: > > "Kevin B. Hendricks" <[EMAIL PROTECTED]> writes: > > > Given their product is heavily based on the hard work of the Blackdown > > team, you would think they would share their diffs. Unfortunately, they > > have refused all requests to share diffs. So much for being the OpenGroup > > (IMHO). > > > > Kevin B. Hendricks > > Linux PowerPC / MkLinux JDK Porting Team > > [EMAIL PROTECTED] > > When you say "heavily based", do you believe they have taken actual code > from the blackdown port? Is the blackdown port GPL (which would make such > borrowing illegal)? > > Liz Coolbaugh > [EMAIL PROTECTED] If the irony in the name "The Open Group" weren't so tragic, it might almost be amusing. -- Ed Huott [EMAIL PROTECTED]
Re: "Open" Group port/Invocation dumps core
Bernd Kreimeier wrote: > > I downloaded the whole bulk for one single purpose: > to check whether this native thread port solves > the problem with the Invocation API and green_threads. > Well, v1 dumps cores on me in all my simple test > programs (whether using dlopen or linking against > libjava), which means that I do not even get as far > as with the Blackdown ports (which dump on "open" calls). Did you follow the Open Group's recommendations for installed versions of all relevant libraries? I'm not an Invocation API user, but if you've got some small sample code, I'll be happy to try it against my installation of the Open Group JDK. > If anybody has gotten the v1 version to work with > the Invocation API, I'd like to hear about it. Until > they decide to cooperate with Blackdown on fixes > and diffs, I am going to ignore the "Open" Group port. > I do not have the time to get back to square one. The Open Group has its own business realities to deal with. Your demand -- that they adopt your favorite business model for sharing source -- seems an awfully harsh one for judging the merit of their efforts. And is it necessarily the fastest or surest way of solving your problems? Nathan Meyers [EMAIL PROTECTED]
(no subject)
unsubscribe
update: JDK1.1.6 segmentation fault fixed by glibc 2.0.7
Hello all, I wrote a few days ago about the problem I was having w/ JDK1.1.6 from blackdown.org. When I executed java, a segmentation fault would happen immediately. I have a RH 5.0 installation. Someone suggested that I download the most recent glibc package, which is 2.0.7, to replace the one which came w/ RH 5.0, which is 2.0.6. At first that didn't help any -- but that's apparently because, after finding that JDK wouldn't run, I installed kaffe. Which did run, although kaffe doesn't include a number of classes, so it's not a complete solution in itself. So after blowing away kaffe, java from the JDK runs fine! I'm very happy about this. I will be doing some RMI programming. (Distributed belief networks -- in case you want to know.) Thanks for the helpful hints. I'm posting this in the hope that this note will help someone in a similar situation. --Robert Dodier
"Open" Group port/Invocation dumps core
I downloaded the whole bulk for one single purpose: to check whether this native thread port solves the problem with the Invocation API and green_threads. Well, v1 dumps cores on me in all my simple test programs (whether using dlopen or linking against libjava), which means that I do not even get as far as with the Blackdown ports (which dump on "open" calls). If anybody has gotten the v1 version to work with the Invocation API, I'd like to hear about it. Until they decide to cooperate with Blackdown on fixes and diffs, I am going to ignore the "Open" Group port. I do not have the time to get back to square one. b. P.S.: JDK 1.1.6v2 gets into an endless number of Tried to free bogus memory 80b36c8, ignored Tried to free bogus memory 80b3708, ignored Tried to free bogus memory 80b3748, ignored when using a simple dlopen/invocation test.
Survey: does this crash your compiler?
Hi,
I've found the miracle handful of lines of code that crash two out of
three compilers I could find *grin*
The contestants:
javac (Blackdown JDK1.1.6v2 on Linux)
javac (Sun JDK1.1.5 on NT)
jikes (on Linux)
sj (the Symantec compiler on WinNT)
The sole survivor:
jikes
Hehehehe :)
dstn.
Caution: compiler death below this line
---
import java.awt.*;
public class DieNow {
public DieNow () {
Panel death = new Panel (null){
public Insets getInsets () {
return new Insets (6,6,6,6);
}
};
}
}
-
Dustin Lang, [EMAIL PROTECTED]
Re: Survey: does this crash your compiler?
NO!
dave and philippe
Jikes co-authors
[EMAIL PROTECTED] on 08/21/98 09:35:37 PM
To: [EMAIL PROTECTED]
cc:(bcc: David Shields/Watson/IBM)
Subject: Survey: does this crash your compiler?
Hi,
I've found the miracle handful of lines of code that crash two out of
three compilers I could find *grin*
The contestants:
javac (Blackdown JDK1.1.6v2 on Linux)
javac (Sun JDK1.1.5 on NT)
jikes (on Linux)
sj (the Symantec compiler on WinNT)
The sole survivor:
jikes
Hehehehe :)
dstn.
Caution: compiler death below this line
---
import java.awt.*;
public class DieNow {
public DieNow () {
Panel death = new Panel (null){
public Insets getInsets () {
return new Insets (6,6,6,6);
}
};
}
}
-
Dustin Lang, [EMAIL PROTECTED]
