[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
 Keywords:             |       Port:
-----------------------+--------------------
 The situation that caused an instance of #67320 was an upgrade of
 `clang-14 +universal`, that thought that it needed `clang-11 +universal`
 to build it.  And the reason that `clang-14` itself was `+universal` was
 most likely due to an earlier occurrence of the same bug.

 I'm not sure if `gcc` needs to be `+universal` to build `+universal`
 targets (I've seen some evidence that it does), but this is certainly not
 true of `clang`.  The only part of `clang` that needs to be built for the
 target architecture is the `compiler-rt` stuff, which is already built for
 multiple architectures regardless of the `universal` variant.  And `llvm`
 normally builds for all supported target architectures, regardless of its
 `universal` variant.

 I think the relevant code is in base, but I could be wrong about that.

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