<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Nov 3, 2023, at 10:42 AM, Philip Race <philip.race@oracle.com> wrote:</div><br class="Apple-interchange-newline"><div><div>Are you referring to some open bug, or some thread somewhere ?<br><br></div></div></blockquote><div><br></div><div>I found several threads that refer to this issue by searching for the error message.</div><div><br></div><div>Demonstrating the issue may require using the screen menu bar.</div><div><br></div><div><div class="errors" style="font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(204, 0, 0); background: rgb(255, 230, 230); margin: 15px 0px; padding: 10px 15px; border: 1px solid rgb(51, 51, 51);"><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
References to Carbon menus are disallowed with AppKit menu system (see rdar://101002625). Use instances of NSMenu and NSMenuItem directly instead.</p></div><div class="errors" style="margin: 15px 0px; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(204, 0, 0); background: rgb(255, 230, 230); padding: 10px 15px; border: 1px solid rgb(51, 51, 51);"><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
0 AppKit 0x193d7e4e4 _NSCarbonMenuCrashIfNeeded + 488</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
1 AppKit 0x193d7e294 _NSGetCarbonMenu + 24</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
2 JavaRuntimeSupport 0x1fb31dde8 -[JRSMenu installCarbonEventHandlers:] + 172</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
3 CoreFoundation 0x18faae820 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
4 CoreFoundation 0x18fb428ec ___CFXRegistrationPost_block_invoke + 88</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
5 CoreFoundation 0x18fb42834 _CFXRegistrationPost + 440</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
6 CoreFoundation 0x18fa7d48c _CFXNotificationPost + 764</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
7 Foundation 0x190b6f030 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88</p><p style="margin-top: 0px; margin-bottom: 0px; white-space: pre;">
8 AppKit 0x193288a50 -[NSMenu insertItem:atIndex:] + 520</p><p style="margin-bottom: 0px; margin-top: 0px; white-space: pre;">
9 Foundation 0x190bde2d8 __NSThreadPerformPerform + 264</p></div></div><div><br></div><div><br></div><blockquote type="cite"><div><div>I've also built JDK 22 on macOS 14 using the macOS 13 SDK (ie Xcode 14.3.1 as downloaded by our internal build<br>support) and had no issues. It reads to me like you may not have a clean build .. but in that case I'm<br>not sure why configure doesn't complain. Did you just 'swap out' the Xcode in a way the build maybe<br>can't spot ?<br><br></div></div></blockquote><div><br></div><div>I followed the directions to use xcode-select. Was I supposed to reconfigure after that? I don’t remember if I did that or just a make clean.</div><div><br></div><div><br></div><div><br></div><br><blockquote type="cite"><div><div>-phil<br><br>On 11/2/23 9:48 AM, Alan Snyder wrote:<br><blockquote type="cite">As you may know, a JDK built on macOS 14 using the macOS 14 SDK crashes during initialization of AWT.<br><br>(The problem appears to be Apple’s bug. It is triggered by a runtime check that is enabled only in programs that were linked against the macOS 14 SDK.)<br><br>So I tried to build JDK using the macOS 13 SDK (specifically, I was building jdk21u).<br><br>I tried both suggestions in the build documentation for configuring the Xcode version.<br><br>The first suggestion was to use xcode-select to select the previous version of Xcode (version 14), which contains the macOS 13 SDK.<br><br>This suggestion is ugly because Xcode 14 does not run on macOS 14, but it might have worked.<br><br>However, the suggestion failed because I started getting warnings like this:<br><br>"The shared archive file was created by a different version or build of HotSpot”<br><br>Even worse, however, is that these warnings *were inserted in generated Java sources*, causing the build to fail.<br><br>For example:<br><br>package sun.awt;<br>public class AWTIcon32_security_icon_interim16_png {<br>public static int[] security_icon_interim16_png = {<br>[0.016s][warning][cds] The shared archive file was created by a different version or build of HotSpot<br>...<br><br>I then tried the second suggestion, configuring with --with-toolchain-path=/Applications/Xcode14.app/Contents/Developer/usr/bin.<br><br>This appears to work.<br><br></blockquote><br></div></div></blockquote></div><br></body></html>