[MacPorts] #69753: openjdk22 @22_0+release+server: insists on being re-built again and again but it is still broken because of /System/Library/Frameworks/JavaRuntimeSupport.framework does not exist

[MacPorts]

#69753: openjdk22 @22_0+release+server: insists on being re-built again and again
but it is still broken because of
/System/Library/Frameworks/JavaRuntimeSupport.framework does not exist
------------------------+----------------------
  Reporter:  JD-Veiga   |      Owner:  breun
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.9.3
Resolution:             |   Keywords:
      Port:  openjdk22  |
------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:3 breun]:
 > I also don't find
 `/System/Library/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport`
 on macOS 14.4.1 arm64, but that doesn't seem to be a problem for building
 `openjdk22`.

 It is normal not to find any system library in the filesystem on macOS 11
 or later:

 https://developer.apple.com/documentation/macos-release-notes/macos-big-
 sur-11_0_1-release-notes

 > New in macOS Big Sur 11.0.1, the system ships with a built-in dynamic
 linker cache of all system-provided libraries. As part of this change,
 copies of dynamic libraries are no longer present on the filesystem. Code
 that attempts to check for dynamic library presence by looking for a file
 at a path or enumerating a directory will fail. Instead, check for library
 presence by attempting to dlopen() the path, which will correctly check
 for the library in the cache. (62986286)

 Replying to [comment:4 JD-Veiga]:
 > Well, building tests are not always accurate according to my experience.
 It is not the first time that I can install a port apparently not
 supported by my OS version (I am talking about Catalina and older
 macOSes). I suppose that some subtle differences between actual systems
 used by users and testing machines make it possible.
 >
 > Obviously, I do not get any of the "error: invalid version number in
 '-mmacosx-version-min=11.00.00'" messages that appear in the macport's
 buildbot log. Maybe they are clang version related? I really do not know.

 I deliberately do not update Xcode and the command line tools to the very
 latest compatible version on most of the buildbot workers. Instead, I keep
 them at the last version that contains that OS version's SDK, because some
 software fails to build when the SDK version does not match the OS
 version. So, for example,
 [https://build.macports.org/buildslaves/ports-10.15_x86_64 as you can see
 here], the macOS 10.15 buildbot worker uses Xcode 11.7, the last version
 that contains the macOS 10.15 SDK, rather than Xcode 12.4, the last
 version compatible with macOS 10.15 but containing the macOS 11 SDK.
 Certainly, Xcode 11.7, having been released before macOS 11, will be
 unable to accommodate a request to build for a minimum macOS version of
 "11.00.00", and software built for a minimum macOS version of 11 would not
 be guaranteed to run on macOS versions earlier than 11.

-- 
Ticket URL: <https://trac.macports.org/ticket/69753#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS