[MacPorts] #58493: cctools: using clang < 5.0 as default assembler generates assembly errors in some cases
MacPorts
noreply at macports.org
Tue May 21 20:31:38 UTC 2019
#58493: cctools: using clang < 5.0 as default assembler generates assembly errors
in some cases
----------------------+----------------------
Reporter: kencu | Owner: jeremyhu
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: cctools |
----------------------+----------------------
Comment (by cjones051073):
Replying to [comment:31 mouse07410]:
> > Xcode’s clang is already part of the check. Nothing needs to change in
this regard
>
> It was my impression that by default it would pick a Macports clang, or
even install it (I'm not sure which Macports component does it though). So
if by default Xcode clang would be used when present - I'm happy, and
nothing needs to change in this regard.
As i have said, a few times now, cctools will never trigger the
installation of any macports clang port. If it fails to find a suitable
one at runtime, xcode clang is used instead. The logic Is this way around,
as we know the macports clang work on all platforms, clang 5.0 is the same
on all, whereas the systems, whereas Xcode clang varies in capabilities.
So the logic is in my view correct.
--
Ticket URL: <https://trac.macports.org/ticket/58493#comment:32>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list