Bring back 10.6 builds? #3
Comments
|
I don't have OSX machine anymore. Le 10 janv. 2013 à 18:36, Lee Hinman notifications@github.com a écrit :
|
|
The first commands with If I run the build anyway, I get this error: |
|
SnowLeopard 32 or 64bits ? XCode version ? AWTWindow' may not respond to '+getNSWindowDisplayID_AppKitThread:' Oracle (and Apple), don't support Snow, so may be it's a missing 2013/1/11 Lee Hinman notifications@github.com
|
|
I suggest you to post a message to openjdk macosx list but I'm unsure 2013/1/11 Henri Gomez henri.gomez@gmail.com
|
|
I reattempted the same steps in order to build OpenJDK 7 on Mac OS X 10.6.8, Let's analyse each of the above errors.
This also explains why binary builds of JDK 1.7, despite numerous how-to's (1, 2) are available, shouldn't be installed onto Mac OS X 10.6 using either Pacifist or PackageMaker — whenever any of the above AWT methods are called, the JVM will crash, as the native implementation wouldn't be available. Unless JDK is intended for pure server-side development (i. e. no AWT), the only viable option for those unwilling to upgrade to Mac OS X 10.7+ is to build OpenJDK with X11 instead of Apple's |
|
Great analysis. May I suggest you to contact openjdk mailing lists, at least http://openjdk.java.net/projects/macosx-port/ |
|
Thanks. Ok I can, but what should I tell those guys? Snow Leopard is no longer supported as a target for JDK 1.7, P. S. The only aim of my original post was to explain why the build fails, as a lot people (myself included) are still following Google's search results and reaching this page in a hope to get JDK working. I didn't intend to bug anyone with issue reports (as there're no issues). |
|
Well, you could try to propose patch to support 10.6 (at least build support) |
|
Okay. Maybe I'll have the patch some day =) |
|
Technically, it is possible to wrap each such implementation with the following code: #if __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ >= 1070
/*
* Original 10.7+ Implementation goes here
*/
#else
const jclass throwable = (*env)->FindClass(env, "java/lang/UnsupportedOperationException");
if (throwable != NULL) {
char message[256];
sprintf(message, "Not implemented in Mac OS X %d", __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__);
(*env)->ThrowNew(env, throwable, message);
}
#endif // __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__This could make the code at least compilable on 10.6.8 Snow Leopard. |
|
your best chance is to try to convince Oracle guys to include this stuff inside base code. |
|
Okay, I got it built, and the JDK can even run some trivial code. Any AWT code, however, results in the following error message followed by a core dump: I'm not an Objective C guru, but the issue seems 10.6-specific (see here). So there's more work ahead, particularly, |
|
Good works. Time to open this discussion to world with a Tweet :) |
|
This is still work in progress, but now I'm finally getting a clean No more JVM crashes =) |
|
Well done. Issue reopened to track your work in progress. If you succeed, provide patch to OpenJDK team. |
|
Finally. As of now, AWT works for me on 10.6 Snow Leopard.
Could you please review those? |
|
PR merged. It's trully a tremendous works you did and I guess you're now the OSX OpenJDK champion for tons of SnowLeopard users. Many thanks and congrats ! |
|
Thank you Henri, and apologies for the delayed response — been busy with other projects. The corresponding discussion at the macosx-port-dev list is here. |
|
Did you get success in mailing list to get your patches applied ? |
|
No, not yet. |
|
I see Mike comments ;( |
|
To me it looks like it didn't happen. I built it from this source anyway, and it's great! Thanks for the hard work, I appreciate it! |
|
Cheers, I'm closing issue |
Part of the draw for using the pre-built OpenJDK builds was that I could use JDK 7 on OSX 10.6 (Since Oracle doesn't support it).
Now that the downloads are gone, and the build instructions require Lion or Mountain Lion, I cannot use JDK 7.
Would it be possible to publish instructions for building on 10.6?
The text was updated successfully, but these errors were encountered: