RFR: 7113349 JDK8 port to macosx

Michael McMahon michael.x.mcmahon at oracle.com
Mon Mar 5 08:05:26 PST 2012

I'm still having problems reproducing this, even with the same boot JDK 
you are using.

I remember the original macosx-port hotspot had a build option called 
So, presumably there has been an issue with this before.

Based on what you say below about possible  issues running an 8 gamma 
with a libjava from 7
is this some kind of boot strapping problem, which may need an option 
like the above
until we get promoted macos builds where the right libjava can be pulled in?
I don't know enough about gamma to know if this makes sense..

- Michael

On 02/03/12 22:46, John Rose wrote:
> On Mar 2, 2012, at 1:28 AM, Michael McMahon wrote:
>> I can't reproduce it. It must be something related to the boot JDK you are using.
>> Is it a complete jdk7 image?
> The JDK files I got via the DYLD_LIBRARY_PATH are in a download from this file:
>    http://download.java.net/jdk7u4/archive/b12/binaries/jdk-7u4-ea-bin-b12-macosx-amd64-16_feb_2012.dmg
> I got it from here:
>    http://jdk7.java.net/macportpreview/
> --------
> 	/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home/bin/java -fullversion
> java full version "1.7.0_04-ea-b12"
> --------
> 	/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home/bin/java -Xinternalversion
> Java HotSpot(TM) 64-Bit Server VM (23.0-b15) for bsd-amd64 JRE (1.7.0_04-ea-b12), built on Feb 16 2012 11:12:32 by "java_re" with gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
> --------
> This is also the ALT_BOOTDIR I use for builds.
> When I built my own copy of hotspot (including gamma) I used a jdk8 repo (hsx/hotspot-comp/{hotspot,jdk,langtools}), plus your patches for 7113349.
> I wouldn't be surprised if there were random problems running a JDK8 gamma on top of a libjava.dylib from 1.7.0_04.
>> I do get a (different) error if I set DYLD_LIBRARY_PATH in the environment
>> Are you actually setting this in your environment?
>> I notice the sanity check isn't looking for this, which it should on Mac.
> No, I don't set that, but the example commands I sent have settings for it.
> What's confusing (but maybe unimportant) is that the bug Stuart and I saw manifests only when libjava is put on the DLLP, but it does not manifest when the same libjava is loaded by some other unknown means.  (The loading can be traced with DYLD_PRINT_LIBRARIES, as shown in my message.)
> — John

More information about the macosx-port-dev mailing list