[MacPorts] #72023: swi-prolog @9.2.9: Patch idea for macOS 10.11.6
MacPorts
noreply at macports.org
Sun Feb 9 00:42:15 UTC 2025
#72023: swi-prolog @9.2.9: Patch idea for macOS 10.11.6
--------------------------+---------------------------
Reporter: kogule | Owner: JanWielemaker
Type: enhancement | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.10.5
Resolution: | Keywords: elcapitan
Port: swi-prolog |
--------------------------+---------------------------
Changes (by ryandesign):
* keywords: => elcapitan
Comment:
Don't close the ticket, please. It's an accurate bug report. swi-prolog
doesn't build on OS X 10.11 and earlier.
If you would like to know which compilers MacPorts believes support each
language standard, see CompilerSelection.
The user's compiler is not misconfigured. It is normal that the system C++
library will be used, even when a newer compiler is used. The system C++
library may not support newer C++ language features.
The [source:macports-ports/_resources/port1.0/group/legacysupport-1.1.tcl
legacy support portgroup] offers the `legacysupport.use_mp_libcxx` option
which can be set to `yes` to indicate that MacPorts should use a newer
MacPorts copy of the C++ library instead for this port. I cannot guarantee
that doing this won't have adverse consequences. For example, I don't know
what happens if any of swi-prolog's dependencies use the system C++
library and swi-prolog uses a newer MacPorts C++ library and objects
created with one library are passed to code using the other library. Back
when the C++ library was GCC's libstdc++ that kind of thing did definitely
cause runtime crashes but I don't know if the same applies to LLVM's
libc++.
--
Ticket URL: <https://trac.macports.org/ticket/72023#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list