https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126962
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> --- This bug seems to occur during the libgfortran build: $ grep "^Config" mk.out Configuring in ./libiberty Configuring in ./lto-plugin Configuring in ./fixincludes Configuring in build-x86_64-pc-linux-gnu/libiberty Configuring in build-x86_64-pc-linux-gnu/fixincludes Configuring in build-x86_64-pc-linux-gnu/libcpp Configuring in ./libbacktrace Configuring in ./zlib Configuring in ./libcody Configuring in ./libdecnumber Configuring in ./c++tools Configuring in ./libcpp Configuring in ./gcc Configuring in ./libcc1 Configuring in x86_64-pc-linux-gnu/libgcc Configuring in x86_64-pc-linux-gnu/libatomic Configuring in x86_64-pc-linux-gnu/libstdc++-v3 Configuring in x86_64-pc-linux-gnu/libgomp Configuring in x86_64-pc-linux-gnu/libbacktrace Configuring in x86_64-pc-linux-gnu/libssp Configuring in x86_64-pc-linux-gnu/libquadmath Configuring in x86_64-pc-linux-gnu/libgfortran $
