[MacPorts] #69138: rust @1.75.0 : Does not build on macOS 10.11.6 - missing _getentropy and _clock_gettime

MacPorts noreply at macports.org
Wed May 29 05:19:09 UTC 2024


#69138: rust @1.75.0 : Does not build on macOS 10.11.6 - missing  _getentropy and
_clock_gettime
------------------------+---------------------------------
  Reporter:  snowflake  |      Owner:  MarcusCalhoun-Lopez
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.8.99
Resolution:  fixed      |   Keywords:
      Port:  rust       |
------------------------+---------------------------------

Comment (by MarcusCalhoun-Lopez):

 Replying to [comment:23 mqudsi]:
 > Thanks for that reference.
 >
 > > Are you asking if `-Wl,/opt/local/lib/libMacportsLegacySystem.B.dylib`
 can be automatically used as a linker flag?
 >
 > Shouldn’t it? Imagine the legacy-support project doesn’t exist. One
 “perfect” patch (from a compatibility and results perspective, not from a
 maintenance or brittleness perspective) would be to patch the std library
 to revert the upstream  removal of the legacy macOS support shims or
 replace the calls to the missing apis with patched equivalents. The result
 would be a rust toolchain that would build everything without any
 workarounds on behalf of the end user, including for non-MP rust projects.
 I would *expect* the same from the workaround that was actually used.
 >
 > The drawback is obviously a runtime dependency on the legacy-support
 libs, but I don’t think that’s an unreasonable trade off. But does it
 break anything else?

 It may be possible and desirable to have
 `-Wl,${prefix}/lib/libMacportsLegacySystem.B.dylib` automatically added.\\
 I am afraid I would have to research this a bit.

-- 
Ticket URL: <https://trac.macports.org/ticket/69138#comment:25>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list