[MacPorts] #69812: cmake-bootstrap @3.9.6 does not compile under rosetta2
MacPorts
noreply at macports.org
Wed Apr 24 23:41:33 UTC 2024
#69812: cmake-bootstrap @3.9.6 does not compile under rosetta2
------------------------------+--------------------
Reporter: lukaso | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: cmake-bootstrap |
------------------------------+--------------------
Comment (by ryandesign):
Replying to [comment:8 lukaso]:
> > If you mean comping for one macOS version on another macOS version, or
for one macOS architecture from another macOS architecture, then yes, with
the caveat that it is not well tested and there are therefore frequent
problems.
>
> How is this done? I might as well try it.
Building for a different OS version, you're already doing by setting
`macosx_deployment_target` in macports.conf I presume. While Apple would
like us to believe that we can build for older OS versions using the
latest SDK, it looks like you're also specifying the older 10.13 SDK by
setting `macosx_sdk_version` in macports.conf.
Building for another arch is done by changing `build_arch` (for non-
universal builds) and `universal_archs` (for universal builds) in
macports.conf.
And I agree with Ken that what you're doing using Rosetta 2 ''should''
work but I don't think anybody has tested it before.
> > The simplest way to do so would be to perform the builds on a machine
that runs macOS 10.13.
>
> I've tried to find ways of doing this. But it's not OK for our builds to
be on a machine under my desk. How does Macports do this? I suppose, if I
had a VM that was properly hosted, I could support even older MacOS
versions.
I run https://build.macports.org from three Xserves running VMware ESXi
with VMs for each OS version.
--
Ticket URL: <https://trac.macports.org/ticket/69812#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list