Unable to build JDK on macOS 10.14.6

[Timmy Jose]

Hey Erik,

Just wanted to confirm (and might be useful for other folks building on
macOS), that updating to Xcode 11.3.x (Version 11.3.1 (11C504) worked:

```
~/dev/forks/openjdk/jdk-jdk/build/macosx-x86_64-server-release/images/jdk/bin$
./javac --version
javac 15-internal

~/dev/forks/openjdk/jdk-jdk/build/macosx-x86_64-server-release/images/jdk/bin$
./java --version
openjdk 15-internal 2020-09-15
OpenJDK Runtime Environment (build 15-internal+0-adhoc.z0ltan.jdk-jdk)
OpenJDK 64-Bit Server VM (build 15-internal+0-adhoc.z0ltan.jdk-jdk, mixed
mode, sharing)
```

Thank you so much for your help again!

Best,

Timmy

On Fri, Feb 28, 2020 at 9:40 PM Timmy Jose <zoltan.jose at gmail.com> wrote:

> Hi Erik,
>
> Thank you for responding so quickly! I will try to get Xcode 11.3 set up
> and give it a go. Thanks for the tip!
>
> Cheers,
>
> Timmy
>
> On Fri, Feb 28, 2020 at 9:38 PM Erik Joelsson <erik.joelsson at oracle.com>
> wrote:
>
>> Hello Timmy,
>>
>> On 2020-02-28 05:32, Timmy Jose wrote:
>> > Hello,
>> >
>> > I have a tarball that I downloaded from
>> > https://builds.shipilev.net/workspaces/jdk-jdk.tar.xz, and was trying
>> to
>> > build the same.
>> I have no idea what version of the source this is, but I'm guessing it's
>> a recent snapshot of our mainline http://hg.openjdk.java.net/jdk/jdk/
>> > This are the commands that I am using to build the project:
>> >
>> > 1. /configure
>> >
>> --with-toolchain-path=/Applications/Xcode.app/Contents/Developer/usr/bin/
>> > --disable-warnings-as-errors, and then
>> You shouldn't need either of those arguments. Configure will find the
>> default Xcode installation automatically.
>> > 2. make images
>> >
>> > My Xcode version is: Version 11.0 (11A420a).
>> I have never tested this version. We use 10.1 at Oracle and I just
>> verified that 11.3 builds OpenJDK without problems. There could be a bug
>> with the 11.0 version that we do not know about.
>> > However, it fails with a strange error about libarclite_macosx.
>> >
>> > ```
>> > Undefined symbols for architecture x86_64:
>> >    "_objc_loadClassref", referenced from:
>> >        __ARCLite__load() in libarclite_macosx.a(arclite.o)
>> > ld: symbol(s) not found for architecture x86_64
>> > clang-9: error: linker command failed with exit code 1 (use -v to see
>> > invocation)
>> > make[3]: ***
>> >
>> [/Users/z0ltan/dev/forks/openjdk/jdk-jdk/build/macosx-x86_64-server-release/support/modules_libs/java.base/libosxsecurity.dylib]
>> > Error 1
>> > make[2]: *** [java.base-libs] Error 2
>> >
>> > ERROR: Build failed for target 'images' in configuration
>> > 'macosx-x86_64-server-release' (exit code 2)
>> >
>> > === Output from failing command(s) repeated here ===
>> > * For target
>> > support_native_java.base_libosxsecurity_BUILD_LIBOSXSECURITY_link:
>> > Undefined symbols for architecture x86_64:
>> >    "_objc_loadClassref", referenced from:
>> >        __ARCLite__load() in libarclite_macosx.a(arclite.o)
>> > ld: symbol(s) not found for architecture x86_64
>> > clang-9: error: linker command failed with exit code 1 (use -v to see
>> > invocation)
>> >
>> > * All command lines available in
>> >
>> /Users/z0ltan/dev/forks/openjdk/jdk-jdk/build/macosx-x86_64-server-release/make-support/failure-logs.
>> > === End of repeated output ===
>> >
>> > No indication of failed target found.
>> > Hint: Try searching the build log for '] Error'.
>> > Hint: See doc/building.html#troubleshooting for assistance.
>> >
>> > make[1]: *** [main] Error 2
>> > make: *** [images] Error 2
>> > ```
>> >
>> > I am attaching the failure logs (LOG=debug) with this email.
>>
>> Attachments are unfortunately stripped by the mailing list so can't see
>> them, but I would recommend trying a different version of Xcode. You can
>> install them side by side if you rename your existing
>> /Applications/Xcode.app to something like /Applications/Xcode-11.0.app
>> before installing the other version. After that you can switch between
>> them using xcode-select.
>>
>> /Erik
>>
>> > If any specific information would be useful in debugging this issue, I
>> > would be more than happy to share the same.
>> >
>> > Best Regards,
>> >
>> > Timmy
>>
>