Thanks for the files, and I've now also reproduced the problem in a `--build=x86_64-unknown-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu` configuration (using system GCC `x86_64-linux-gnu-gcc` etc., and approximately matching GCC sources).
The proposed "libgomp: Fix gfortran detection when program is found via PATH" patch has the issue that it picks up the "gfortran [...] found via PATH" also in the case when GCC is configured without `--enable-languages=fortran` in effect, and it then still builds and installs the libgomp/Fortran support files in GCC configurations without Fortran support enabled. Please test <https://inbox.sourceware.org/[email protected]> "libgomp: Revise libgomp/Fortran support conditionals", which should achieve the same thing, but in a conceptually simpler way. -- https://forge.sourceware.org/gcc/gcc/pulls/172#issuecomment-6950
