[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
noreply at macports.org
Fri Jun 7 07:13:21 UTC 2024
#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
Resolution: | Keywords: sonoma
Port: |
---------------------------+--------------------
Comment (by jmroot):
Replying to [comment:2 MSoegtropIMC]:
> so this is more a general precaution than based on observations with the
specific compiler and OS versions mentioned in
/opt/local/libexec/macports/lib/port1.0/portutil.tcl ?
Every case where the "ok" version is higher than "min" was added because
of specific serious bugs that affected port builds.
> Looking at the MacPorts code, I don't think setting
configure.sdk_version or macosx_deployment_target in all ports I use would
prevent the error.
No, that would be in addition to the local modifications you made to base.
BTW, if you really want to lie to MacPorts about what version of Xcode you
have installed (hopefully understanding and accepting the consequences),
you can override xcodeversion in macports.conf. Please just don't report
any bugs after doing so.
To allow you to use an older toolchain locally, you could most likely just
install older Command Line Tools, as that is what most ports use anyway.
You can also install multiple versions of Xcode at the same time and
switch between them with xcode-select.
Requiring users (and buildbots) to install an older version of Xcode when
building certain ports is not going to be a workable general solution.
--
Ticket URL: <https://trac.macports.org/ticket/70182#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list