[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:  (none)
     Type:  defect    |     Status:  new
 Priority:  Normal    |  Milestone:
Component:  ports     |    Version:  2.9.3
 Keywords:            |       Port:  @openjdk22
----------------------+------------------------
 Hi,

 I have installed `openjdk2` in macOS 10.15.7 (Catalina) without any
 problem. However, when rev-upgrade is checked **it claims that `openjdk22`
 is broken and must be re-built**. Re-building does not solve the problem
 since **`openjdk22` is still broken after the process is completed**.


 {{{
 Could not open
 /System/Library/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport:
 Error opening or reading file (referenced from
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libawt.dylib)
 --->  Found 6 broken files, matching files to ports
 Error: Port openjdk22 is still broken after rebuilding it more than 3
 times.
 }}}

 Running `port -d -y rev-upgrade` yields the following report (only errors
 are shown here):

 {{{
 [...]
 Could not open
 /System/Library/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport:
 Error opening or reading file (referenced from
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libawt.dylib)
 DEBUG: Marking
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libawt.dylib
 as broken
 [...]
 DEBUG: Ignoring loadcommand containing @rpath in
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libawt_lwawt.dylib
 DEBUG: Marking
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libawt_lwawt.dylib
 as broken
 [...]
 DEBUG: Marking
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libosx.dylib
 as broken
 [...]
 DEBUG: Marking
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libosxapp.dylib
 as broken
 [...]
 DEBUG: Marking
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libosxui.dylib
 as broken
 [...]
 DEBUG: Marking
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libsaproc.dylib
 as broken
 [...]
 }}}

 So, it seems that the problem is :
 {{{
 Could not open
 /System/Library/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport:
 Error opening or reading file (referenced from
 /opt/local/Library/Java/JavaVirtualMachines/jdk-22-macports.jdk/Contents/Home/lib/libawt.dylib)
 }}}

 Actually,
 `/System/Library/Frameworks/JavaRuntimeSupport.framework/Versions/A/JavaRuntimeSupport`
 does not exit in my system at all. Indeed, **parent directory
 `/System/Library/Frameworks/JavaRuntimeSupport.framework` does not
 exist**.

 I wonder if the installation process should create that
 `/System/Library/Frameworks/JavaRuntimeSupport.framework` directory in my
 system (or do not search for this directory in `libawt.dylib`).

 Thank you.

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