Changes between Version 1 and Version 2 of Ticket #61636, comment 14
- Timestamp:
- Nov 24, 2020, 5:25:29 AM (4 years ago)
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.1 Oh dear; you should not be using anything other than {{{ld64 +ld64_xcode}}} on newer systems. 2 2 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. 4 4 5 If you presently have {{{ld64}}} installed with any variant OTHERthan {{{ld64 +ld64_xcode}}} please do this:5 If you presently have {{{ld64}}} installed with any variant other than {{{ld64 +ld64_xcode}}} please do this: 6 6 7 7 {{{ … … 10 10 }}} 11 11 12 and you SHOULDget {{{ld64 +ld64_xcode}}}12 and you hopefully will get {{{ld64 +ld64_xcode}}} 13 13 14 if you do NOT get that, we have some work to do. Which we might well have to do.14 if you do not get that, -- oops, we have some work to do (which we might well have to do). 15 15 16 By the way, gcc10 will NOTbuild 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.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. 17 17 18 18 At 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.