[MacPorts] #70217: aom @3.9.0 +universal: ld: Assertion failed: (name != NULL) on 10.9 Mavericks when the linker has been manually set to ld64-xcode.

[MacPorts]

#70217: aom @3.9.0 +universal: ld: Assertion failed: (name != NULL) on 10.9
Mavericks when the linker has been manually set to ld64-xcode.
-------------------------+--------------------
  Reporter:  ar-an-ribe  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.9.3
Resolution:              |   Keywords:
      Port:  aom         |
-------------------------+--------------------

Comment (by kencu):

 Replying to [comment:4 ar-an-ribe]:

 >  On Mavericks, are there any known issues with the `ld64-236.4` version
 of `ld`?

 It gets a bit complicated.

 Certain software, like llvm / clang and gcc, will configure themselves
 based on the linker characteristics they see when they are built. They
 don't expect the linker to be downgraded later.

 So if you then upgrade to a linker that is newer than the one that was
 active when they were built, things are usually OK.

 But if you somehow downgrade the active linker, for example by switching
 macports ld64 port to the the +ld64_xcode variant, then you have a
 problem. The software has been configured to expect a newer linker and
 newer features, and will not usually retest the linker characteristics
 every time it is run -- so it generates code / objects which cause older
 linkers to error.

 Which I suspect is what is happening to you, as in another ticket you have
 revealed having {{{ld64 +ld64_xcode}}} as your active linker, and that is
 a very old linker indeed.

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