MacOSX port build issues

[Mike Swingler]

On Mar 14, 2011, at 9:55 AM, Artem Ananiev wrote:

> Hi, team,
> 
> below is a list of issues I faced when building macosx-port. I'd like to hear your opinion, whether these are bugs or features, should I file new requests in OpenJDK bugzilla (or whatever bug tracking system we decide to use), etc.

It may make sense to setup a temporary project on java.net to use the bug system while the OpenJDK project is still collecting requirements for it's next bug system beyond bugs.openjdk.java.net.

> 1. On Windows I often clone jdk7/awt/jdk and build it separately from all other OpenJDK parts (hotspot, jaxp, jaxws and corba). On Mac, I can only build the whole forest.

Has anyone else had success in building just the JDK tree in isolation for the macosx-port? I think there may be some definitions in the top-level Makefile that the jdk tree is assuming are defined.

> 2. HotSpot build creates folders named bsd_*, which is obviously a BSD port legacy.

Actually, we are fine with this. Since Mac OS X is from the BSD lineage, and we do not plan to use many if any Mac OS X-specific APIs in HotSpot, it is completely accurate to say that the output of those directories is a "BSD HotSpot" compiled as Mach-o binary.

> 3. Flags to pass to make: SA_APPLE_BOOT_JAVA, ALWAYS_PASS_TEST_GAMMA, ALLOW_DOWNLOADS - look like hacks/workarounds for some problems. For example, test_gamma fails because it just can't find JRE to launch. I would like to have this issues filed as bugs, so any person who would like to contribute to the project can easily find a task to do.

The SA_APPLE_BOOT and test gamma hack is a workaround for bootstrapping the build of OpenJDK 7 with our proprietary Java SE 6 on Mac OS X. If you bootstrap OpenJDK 7 with a pre-build OpenJDK 7, neither of those should be necessary.

IIRC, ALLOW_DOWNLOADS just short-circuits the JAXP, JAXWS, etc builds and downloads their jars directly.

Regards,
Mike Swingler
Java Engineering
Apple Inc.