[MacPorts] #61494: gcc9 @9.3.0 "Failed to build libgcc9: command execution failed" in macOS 11.0 Big Sur

[MacPorts]

#61494: gcc9 @9.3.0 "Failed to build libgcc9: command execution failed" in macOS
11.0 Big Sur
-------------------------+--------------------
  Reporter:  kgerheiser  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.4
Resolution:              |   Keywords:  bigsur
      Port:  libgcc9     |
-------------------------+--------------------

Comment (by cjones051073):

 Interesting, the issue also seems to affect gcc10, as I cannot see the as
 an lib there either.

 {{{
 > port content libgcc10
 <sbip>
  /opt/local/lib/libgcc/libatomic.1.dylib
   /opt/local/lib/libgcc/libgcc_ext.10.4.dylib
   /opt/local/lib/libgcc/libgcc_ext.10.5.dylib
   /opt/local/lib/libgcc/libgcc_s.1.dylib
   /opt/local/lib/libgcc/libgfortran.5.dylib
   /opt/local/lib/libgcc/libgomp.1.dylib
   /opt/local/lib/libgcc/libitm.1.dylib
   /opt/local/lib/libgcc/libobjc-gnu.4.dylib
   /opt/local/lib/libgcc/libquadmath.0.dylib
   /opt/local/lib/libgcc/libssp.0.dylib
   /opt/local/lib/libgcc/libstdc++.6.dylib
   /opt/local/lib/libstdc++.6.dylib
 }}}

 this didn't cause any problems there, as there are other files so destroy
 still works. with gcc9 as it was the only file that fails, as destroy
 requires at least one file.

 Until someone works out why the as an lib is not being made, adding a stub
 file to libgcc9 would be a work around.

 Note the the asan lib is for the address sanitiser, so is not a critical
 part needed for the compiler to work...

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