I think it's this place in the build where the logs/warning written out
to stdout gets put into the generated source file
https://github.com/openjdk/jdk/blob/master/make/modules/java.desktop/gensrc/GensrcIcons.gmk#L85
(there are few more places in that same file which have similar calls).
-Jai
We only just switched to macos 13 SDK a few of weeks ago, so the next
upgrade is probably a year away.
I can't see us popping up a user dialog. Even for a UI app. That would
cause additional problems.
But when we see a fix for this on the Apple side, then we'll be able to
make a more informed de
> On Nov 3, 2023, at 2:51 PM, Philip Race wrote:
>
> So, yes, it is a bug on the Apple side and will be fixed in (I think) a macOS
> 14 update.
>
> -phil.
So, how long do you think the JDK can continue using the macOS 13 SDK? Until
macOS 14 is no longer supported?
As soon as the JDK start
On 2023-11-03 21:09, Alan Snyder wrote:
On Nov 3, 2023, at 11:54 AM, erik.joels...@oracle.com wrote:
If you change out the toolchain through xcode-select, then you definitely need
to reconfigure after. I would expect the configuration to be quite messed up if
you don’t..
OK, but I think i
So, yes, it is a bug on the Apple side and will be fixed in (I think) a
macOS 14 update.
-phil.
On 11/3/23 2:28 PM, Philip Race wrote:
So, in the stack trace you posted ..
> JavaRuntimeSupport 0x1fb31dde8 -[JRSMenu installCarbonEventHandlers:]
-phil
On 11/3/23 1:07 PM, Alan Snyder wrote:
So, in the stack trace you posted ..
> JavaRuntimeSupport 0x1fb31dde8 -[JRSMenu installCarbonEventHandlers:]
-phil
On 11/3/23 1:07 PM, Alan Snyder wrote:
On Nov 3, 2023, at 12:20 PM, Philip Race wrote:
It seems likely since it comes along with the updated SDK but did you
have any more e
> On Nov 3, 2023, at 11:54 AM, erik.joels...@oracle.com wrote:
>
> If you change out the toolchain through xcode-select, then you definitely
> need to reconfigure after. I would expect the configuration to be quite
> messed up if you don’t..
>
OK, but I think it is a bug when an error messa
> On Nov 3, 2023, at 12:20 PM, Philip Race wrote:
>
> It seems likely since it comes along with the updated SDK but did you have
> any more evidence than that ?
Because the (inappropriate) call is coming from JRS.
It looks like one of those obsolete API checks that is escalated to a fatal
e
Specifying -Dapple.laf.useScreenMenuBar=true then I do see a crash.
I don't see the message you reported, but it crashes right away - only
for Xcode 15 builds.
I filed https://bugs.openjdk.org/browse/JDK-8319420 to track this.
Why did you say it is an Apple bug ?
It seems likely since it comes
On 11/3/23 11:18, Alan Snyder wrote:
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.
If you change out the toolchain through xcode-select, then you
definitely need to reconfigure after. I would e
> On Nov 3, 2023, at 10:42 AM, Philip Race wrote:
>
> Are you referring to some open bug, or some thread somewhere ?
>
I found several threads that refer to this issue by searching for the error
message.
Demonstrating the issue may require using the screen menu bar.
References to Carbon m
be precise) and I don't
get a crash.
SwingSet2 starts up and runs just fine in my quick testing.
So no issues other than the known warning (not a crash) about secure
coding and that is not related
to building on macOS 14, its about running on macOS14 if you used Xcode
14 or later to build on
As you may know, a JDK built on macOS 14 using the macOS 14 SDK crashes during
initialization of AWT.
(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.)
So I tried to build JDK using the macOS 1
13 matches
Mail list logo
