[MacPorts] #62252: rust @1.47.0_0: Failed to build rust: command execution failed
MacPorts
noreply at macports.org
Thu Apr 8 07:49:49 UTC 2021
#62252: rust @1.47.0_0: Failed to build rust: command execution failed
------------------------+--------------------
Reporter: macdeport | Owner: g5pw
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.6.4
Resolution: fixed | Keywords:
Port: rust |
------------------------+--------------------
Comment (by kencu):
Yes, perhaps -- the sysconf fixes in legacysupport are robust enough to be
used instead of the ones in libSystem on these rare occasions I think.
In clang-devel I will use our sysconf blocker to prevent it being found to
fix this...I can't think of a way to do a current system test in
headers...just a current SDK test, which is not sufficiently good to use.
Runtime system branching is tricky, esp when a weak linked symbol won't do
it as the symbol exists, you just want to override it.
The new {{{__available() }}} builtins would be just wonderful for this, if
the old system compilers would compile them, but they won't
Actually, probably I could pull that from clang-rt. That is where I last
got to in the thought process about this.
--
Ticket URL: <https://trac.macports.org/ticket/62252#comment:21>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list