[MacPorts] #70217: aom @3.9.0 +universal: ld: Assertion failed: (name != NULL)

[MacPorts]

#70217: aom @3.9.0 +universal: ld: Assertion failed: (name != NULL)
-------------------------+--------------------
  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:2 ar-an-ribe]:
 > Replying to [comment:1 kencu]:
 > > So far, in all cases it seems to be caused by a misconfigured build
 that ultimately tries to invoke /usr/bin/ld to do the link.
 >
 > By a “misconfigured build”, do you mean some configuration on the
 compiling system that needs to be corrected, or some aspect of a given
 port’s `Portfile`, or something else?

 yes.

 :>

 Exactly what is to be sorted out. Usually someone with a similar system
 will attempt the same build and see what happens. If it reproduces on that
 user's system, it's a MacPorts thing usually. If not, it's usually
 something hosed on the user's system. Both things are common -- many users
 have inconsistent system setups, even if they don't know it and (usually)
 swear their system is perfect ... often it is not.


 >
 > > to make any headway, you’d need to attach the main.log to your
 tickets.
 >
 > I’ll attach their respective `main.log` files accordingly.

 Thanks!

 >
 > > Do you really need “universal” variants for everything? This is
 causing you to build everything, which brings headaches.
 >
 > I prefer to build ports with the `+universal` variant when it’s
 available; sometimes that reveals things that would otherwise remain
 undiscovered. (For example, the `policykit` port has a `+universal`
 variant, but it can’t currently be built with that variant, because one of
 its library dependencies, `duktape`, doesn’t have a `+universal` variant
 itself.)

 This is true, but at your stage, it's not too likely you can fix things.
 Ergo frustration.

 It's fine by us -- the reports are useful enough -- but depends on what
 you feel you can put up with.

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