[MacPorts] #67637: Universal builds with clang erroneously require clang itself to be universal

[MacPorts]

#67637: Universal builds with clang erroneously require clang itself to be
universal
------------------------+--------------------
  Reporter:  fhgwright  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.8.1
Resolution:             |   Keywords:
      Port:             |
------------------------+--------------------

Comment (by jmroot):

 Replying to [comment:2 fhgwright]:
 > Getting back to the exact state where this happened might be nontrivial,
 but I believe it involved a case where the chosen compiler was either
 uninstalled or outdated at the time, and when it decided to install or
 upgrade it, it specified `+universal`, probably inherited from the
 original upgrade target.  That's not the same as your test case above,
 where the chosen compiler is already active and up to date.

 OK, so that's the behaviour of all variants explicitly requested on the
 command line: they are applied to dependencies as well as the requested
 port. This might be considered a duplicate of #48051?

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