JDK build on Mountain Lion

[Dan Smith]

Thanks.  This was useful.  Similar experience for me, except 'make sanity' failed immediately because of the X11 freetype dependency.

Following these hints, I was able to successfully build jdk8/jdk8 on a fresh Mountain Lion install by doing the following:

- Get the Xcode application from the App Store
- Launch Xcode and find the setting to install the command-line tools
- Download/install Java 7 (might have survived with the pre-installed Java 6)
- Install XQuartz-2.7.2
- export CPATH="/usr/X11/include" (different than '/usr/include/X11', below, but this seems to be the right place)
- Normal settings for LANG, ALT_BOOTDIR

Glad to see that I don't seem to have to mess with ALT_DROPS_DIR anymore!

Build completed in about 25 minutes on a MacBook Pro.

—Dan

On Jul 27, 2012, at 11:48 AM, Kelly O'Hair <kelly.ohair at oracle.com> wrote:

> Some interesting information on anyone trying to build OpenJDK on Mountain Lion...  10.8 I assume.
> 
> -kto
> 
> Begin forwarded message:
> 
>> From: Naoto Sato <naoto.sato at oracle.com>
>> Subject: JDK build on Mountain Lion
>> Date: July 27, 2012 9:52:02 AM PDT
>> To: Kelly O'Hair <kelly.ohair at oracle.com>
>> Cc: JAVA_I18N_WW_grp at oracle.com
>> 
>> Hi Kelly,
>> 
>> This is just fyi. I just upgraded my MBP to Mountain Lion, and tried to build JDK8 on it. Obviously, Apple removed all the X11 stuff from XCode by default and initially it failed somewhere building AWT.
>> 
>> X11 stuff has been installed when I ran some X11 app (like Java runtime, Apple now installs a stub X11 server which just pops up a message box that urges the user to install 3rd party X11 stuff - XQuarz)
>> 
>> There is another hiccup with it. That is, the default include search path for the C compiler. Now that the X11 stuff is not included in Mountain Lion, /usr/include/X11 is no longer searched. I had to set it with "CPATH" environment variable. Maybe this is something that JDK build script could help.
>> 
>> Naoto
>