[MacPorts] #70182: MacPorts 2.9.3 (base): Xcode 15.X causes issues with some OCaml software (segfaults), but MacPorts does not allow Xcode 14.X on Sonoma

[MacPorts]

#70182: MacPorts 2.9.3 (base): Xcode 15.X causes issues with some OCaml software
(segfaults), but MacPorts does not allow Xcode 14.X on Sonoma
--------------------------+--------------------
 Reporter:  MSoegtropIMC  |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  base          |    Version:  2.9.3
 Keywords:  sonoma        |       Port:
--------------------------+--------------------
 I am maintaining the multi platform distribution of an interactive proof
 assistant (Coq Platform) and I am using MacPorts to install common
 libraries (via opam).

 For yet unknown reasons, when OCaml and Coq are compiled with XCode 15.X -
 or any MacPorts supplied clang using the framework from XCode 15.X, Coq
 segfaults in rare cases. With XCode 14.3.1 and pretty much all previous
 versions of XCode there is no such problem (Coq has a fairly broad user
 base compiling from sources, so there is good evidence for this).

 So I would like to use Xcode 14.3.1, but this conflicts with the settings
 in /opt/local/libexec/macports/lib/port1.0/portutil.tcl - on Sonoma this
 requires Xcode 15.X.

 I wonder where these restrictions come from. Sure Xcode 14 cannot create
 software targeting the Sonoma version of the SDK, but I doubt that a lot
 of MacPorts provided software makes use of latest MacOS features. The
 official Apple docs on MacOS Xcode version compatibility do not mention a
 lower bound for Xcode on Sonoma:

     https://developer.apple.com/support/xcode

 Have there been actual problems with compiling MacPorts supplied software
 with Xcode 14.3.1 on Sonoma?

 I patched the files and then get a message:

     Warning: The macOS 14 SDK does not appear to be installed. Ports may
 not build correctly.

 even though I export MACOSX_DEPLOYMENT_TARGET=11.0. Why does MacPorts
 insist on MacOS 14.X as deployment target? Again I have doubts that this
 makes any difference at all for most MacPorts supplied software packages
 and very little difference for those where it makes a difference. As the
 name implies, MacPorts is there to port software written for other OSes to
 MacOS, which naturally don't use advanced MacOS features. From my desk
 these restrictions look overly strict and at least for me cause more
 problems than good.

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