JDK mainline build fails on macosx with XCode 16

[Magnus Ihse Bursie]

On 2024-09-20 06:44, Jaikiran Pai wrote:

> At this point, there is a workaround (also noted in the JDK-8340341 
> issue and the workaround patch attached to that issue), but my 
> personal recommendation would be to stay with older versions of Xcode 
> that work, because even with the workaround it's unknown whether this 
> compiler issue has wider implications in other places of the JDK.

This would also be a good time to remind everyone about the build 
instructions[1] regarding macOS. They state:

> When updating Xcode, it is advisable to keep an older version for 
> building the JDK. To use a specific version of Xcode you have multiple 
> options:
>
>   * Use |xcode-select -s| before running |configure|, e.g.
>     |xcode-select -s /Applications/Xcode13.1.app|. The drawback is
>     that the setting is system wide and you may have to revert it
>     after a JDK build.
>   * Use configure option |--with-xcode-path|, e.g. |configure
>     --with-xcode-path=/Applications/Xcode13.1.app| This allows using a
>     specific Xcode version for a JDK build, independently of the
>     active Xcode version by |xcode-select|.
>
That means, you should basically always keep your old version of Xcode 
before upgrading, by e.g. renaming it to /Applications/Xcode<version>, 
or moving it out of /Applications. This is not the first time an Xcode 
upgrade broken the JDK build, it it is likely not the last time either.

/Magnus

[1] https://openjdk.org/groups/build/doc/building.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20241007/f021c1a8/attachment-0001.htm>