libgcc11 @11.1.0_2: build fails, impacts other ports

[gorticus (Jason Mitchell)]

libgcc11 @11.1.0_2 build fails:

...
:info:build /bin/sh ../libtool <snip> [...]/libgcc11/work/gcc-11.1.0/libstdc++-v3/libsupc++/bad_cast.cc
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [array_type_info.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** Waiting for unfinished jobs....
:info:build make[5]: *** [atexit_arm.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [atexit_thread.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [atomicity.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [bad_alloc.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [bad_array_length.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [bad_array_new.lo] Error 127
:info:build /bin/sh: ../libtool: No such file or directory
:info:build make[5]: *** [bad_cast.lo] Error 127

Since this impacts libgfortran, it prevents OpenBLAS @0.3.15_5 from building, impacting py3{8,9}-numpy @1.20.3, py3{8,9}-ipython @7.23.1_1, etc.

[gorticus (Jason Mitchell)]

libgcc11 @11.1.0_2 build log (compressed)

[gorticus (Jason Mitchell)]

Forgot to include the platform specifics:

:debug:sysinfo macOS 11.3 (darwin/20.4.0) arch i386
:debug:sysinfo MacPorts 2.6.4
:debug:sysinfo Xcode 12.5
:debug:sysinfo SDK 11.3
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 11.3

uname: 20.4.0 Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64 x86_64

[ryandesign (Ryan Carsten Schmidt)]

According to the log, you started building libgcc11, then you interrupted it, then you retried the build from where it left off and that failed. Therefore, sudo port clean libgcc11 and try again without interrupting it.

In the mean time, we have a binary of this port for your OS version and architecture, so by cleaning and trying again you should receive that and not have to build it on your system.

[gorticus (Jason Mitchell)]

I stand corrected. Double clean fixed and pull binary. Good to close.

[mascguy (Christopher Nielsen)]

Great, glad that your issue is resolved! Closing.