[MacPorts] #64922: gcc10-bootstrap @10.3.0_4 failed at destroot on Leopard

[MacPorts]

#64922: gcc10-bootstrap @10.3.0_4 failed at destroot on Leopard
------------------------------+-------------------------------------
  Reporter:  barracuda156     |      Owner:  catap
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.7.2
Resolution:                   |   Keywords:  powerpc, leopard, ppc64
      Port:  gcc10-bootstrap  |
------------------------------+-------------------------------------

Comment (by Gcenx):

 Replying to [comment:20 kencu]:
 > not really a waste, as you have to build libgcc both times anyway :)

 Doesn’t multilib end up compiling twice in that case?

 \\

 > problem with your cross-compiler method is it works differently than
 every other gcc compiler works now, so nobody, eg barracuda here, will
 understand how the heck to use it. Ergo, more and more and more endless
 tickets.

 As the gcc10-bootstrap provides usage instructions in the notes section
 wouldn’t this fall under user error?

 As this isn’t intended to replace a standard macports compiler it
 shouldn’t be used as such.

 \\

 > OTOH, as a cross-arch compiler, it works.

 If it didn’t I’d have been surprised lol

 \\

 > OTOOH, cross-arch compiling will NEVER work smoothly in MacPorts with
 gcc until somebody updates driverdriver.c to make it work like clang
 works, in the existing infrastructure.
 >
 > SO… it’s all a kludgey mess until that happens.

 Unless someone like iains does this I don’t see driverdriver getting fixed
 up.

 However as this is intended to get libcxx working on 10.6 and be used to
 quickly get to a fully functional macports compiler toolchain should this
 even matter?, I’d be more included for forgo the muniversal group and
 simply build for the current architecture.

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