Changes between Version 1 and Version 2 of Ticket #61636, comment 14


Ignore:
Timestamp:
Nov 24, 2020, 5:25:29 AM (4 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #61636, comment 14

    v1 v2  
    1 You should not be using anything other than {{{ld64 +ld64_xcode}}} on newer systems.
     1Oh dear; you should not be using anything other than {{{ld64 +ld64_xcode}}} on newer systems.
    22
    3 {{{ld64 +ld64_xcode}}} doesn't build or need llvm, or need to be updated to ld64-530 -- it is just a few symlinks into xcode.
     3{{{ld64 +ld64_xcode}}} doesn't build or need llvm -- it is just a few symlinks into xcode.
    44
    5 If you presently have {{{ld64}}} installed with any variant OTHER than {{{ld64 +ld64_xcode}}} please do this:
     5If you presently have {{{ld64}}} installed with any variant other than {{{ld64 +ld64_xcode}}} please do this:
    66
    77{{{
     
    1010}}}
    1111
    12 and you SHOULD get {{{ld64 +ld64_xcode}}}
     12and you hopefully will get {{{ld64 +ld64_xcode}}}
    1313
    14 if you do NOT get that, we have some work to do. Which we might well have to do.
     14if you do not get that, -- oops, we have some work to do (which we might well have to do).
    1515
    16 By the way, gcc10 will NOT build for arm64 at present. We do have a nearly-working fork of gcc-devel that is written by GCC's darwin lead that we are desperately trying to get working on Apple Silicon.
     16By the way, gcc10 will not build for arm64 at present. We do have a nearly-working fork of gcc-devel that is written by GCC's darwin lead that we are desperately trying to get working on Apple Silicon.
    1717
    1818At this moment, it builds neat, on the system, but does not build inside MacPort's infrastructure, so that is where we are with that at present.