Replies: 4 comments · 7 replies
-
Probably. We have all the tools packaged. So, barring bugs.... |
Beta Was this translation helpful? Give feedback.
All reactions
-
@catap Now we just need to fix a broken |
Beta Was this translation helpful? Give feedback.
All reactions
-
So, an obvious reason why thsi can't work, after a year of experience, is that the OpenJDK bootstrap process requires tools.jar from the bootstrap JDK. And we don't distribute that. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@catap Apparently we got only two reasonable options, unless GCC upstream fixes gccj: either fix building from OpenJDK7 or via IcedTea. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Well, I think bootstrapping is the least of your concerns, as that has nothing to do with AWT. You can bootstrap with any working JDK that is at least JDK7. And even then, all you need are some basic tools: java, javac, rmic, and tools.jar. Whether OpenJDK 8 can build targeting OS X PPC is a separate matter. And yeah, upstream appears to have dropped support for that. So that's maintaining a port. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@wasabii The build of OpenJDK 8 was failing after quite some time of running when it reached AWT (there were a few breakages prior to that, but those we have fixed). So perhaps I used the wrong term then: bootrapping works, but the build of the full JDK fails. (Sorry, I am not an expert in its build system.)
In principle that could be restored, but quite likely we will need to build it as for pure BSD/Unix, with X11 and without Cocoa. I do not know how to do that: it seems that there is no configure option (or if there were, it failed to have an effect). |
Beta Was this translation helpful? Give feedback.
All reactions
-
Yeah. You'd have to actually fix that code if you wanted it to work. The C/ObjC code. Or strip out the classes that are OS X specific and broken. Stripping the broken stuff out is probably not too hard. Fixing it would be. Simple fact is the code has moved on, and now relies on stuff that doesn't exist in your target. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
@wasabii Okay, I digged a log from one of build attempts (away from the machine at the moment):
This may not be original failure, but it gives an idea where roughly it got stuck. |
Beta Was this translation helpful? Give feedback.
All reactions
-
There isn't. You'd have to fix the build files. Because in reality, you wouldn't be building it for BSD/Unix. You'd be adding X11 support to OSX (which is disabled on OS X in JDK8), but keeping all the other OS X stuff, like preferences management, IO, etc. The X11 code path I don't believe has ever been enabled for OS X, so chances are it doesn't take into consideration anything related to OS X: https://github.com/openjdk/jdk8u/blob/78c0afa3281b59d2f9cb8675a66b839bd4e7747b/jdk/make/lib/Awt2dLibraries.gmk#L221 So you'd need to patch that up. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
I'm wondering is it possible to bootstrap OpenJDK by using IKVM as bootstrap java?
Has anyone tried it?
Beta Was this translation helpful? Give feedback.
All reactions