<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>On 2024-09-20 06:44, Jaikiran Pai wrote:</p>
<blockquote type="cite" cite="mid:e09f4c75-9403-443f-b9f6-f4d38f9e0427@gmail.com">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.
<br>
</blockquote>
<p>This would also be a good time to remind everyone about the build
instructions[1] regarding macOS. They state:</p>
<p>
<blockquote type="cite">
<p>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:</p>
<ul>
<li>Use <code>xcode-select -s</code> before running
<code>configure</code>, e.g.
<code>xcode-select -s /Applications/Xcode13.1.app</code>.
The drawback
is that the setting is system wide and you may have to
revert it after a
JDK build.</li>
<li>Use configure option <code>--with-xcode-path</code>, e.g.
<code>configure
--with-xcode-path=/Applications/Xcode13.1.app</code>
This allows using a specific Xcode version for a JDK build,
independently of the active Xcode version by
<code>xcode-select</code>.</li>
</ul>
</blockquote>
</p>
<p>That means, you should basically always keep your old version of
Xcode before upgrading, by e.g. renaming it to <font face="monospace">/Applications/Xcode<version></font>, or
moving it out of <font face="monospace">/Applications</font>.
This is not the first time an Xcode upgrade broken the JDK build,
it it is likely not the last time either.</p>
<p>/Magnus<br>
</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://openjdk.org/groups/build/doc/building.html">https://openjdk.org/groups/build/doc/building.html</a><br>
</p>
<br>
</body>
</html>