building OpenJDK on Mac OS X 1.5.8?
Kelly.Ohair at Sun.COM
Thu Nov 5 08:41:45 PST 2009
Just some background.
ALT_BOOTDIR is required and is usually the previously released jdk,
in this case any jdk6 should work, but a jdk7 should work too, assuming
it's not jdk7 b74 :^( Heck, a jdk5 might even work.
ALT_JDK_IMPORT_DIR is only needed when just building part of the
entire openjdk forest, and usually needs to refer to a jdk release that
is of the same vintage as the jdk you are building, e.g. jdk7.
But you might be able to get away with a jdk6 in some situations.
Again, if you are building the entire openjdk forest, ALT_JDK_IMPORT_DIR
should not be needed, or if set, should not be used at all.
Normally in a full forest build, the javac used comes from a langtools
repository build (refer to LANGTOOLS_DIST in the makefiles) run with
the ALT_BOOTDIR java VM. If langtools isn't available, the
ALT_JDK_IMPORT_DIR javac will be used, not the ALT_BOOTDIR one,
because we need to be able to pass in -target 7, which
the ALT_BOOTDIR javac does not normally understand.
So unless the -target 7 options were turned off, ALT_JDK_IMPORT_DIR being
jdk6 might not work.
Hope that helps a bit...
Mario Torre wrote:
> Il 05/11/2009 11:56, Andrei Dmitriev ha scritto:
>> well, that looks a bit different than the discussing thread. I'd say
>> it's more with the value of JAVAH_CMD which equals to
>> May you try to explicitly set it and rebuild? BTW, perhaps the better
>> fix would be to set SLASH_JAVA (ALT_SLASH_JAVA).
> Hi Andrei!
> Ugh! Because I replied to the wrong thread :)
> There is another thread about building on OS X :P
> Anyway, I think I know this guy, try to set this:
> export ALT_BOOTDIR=/usr/lib/jvm/java-1.6.0
> export ALT_JDK_IMPORT_PATH=$ALT_BOOTDIR
> Of course, with ALT_BOOTDIR being something meaningful for you.
More information about the build-dev