https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
--- Comment #1 from Mojca Miklavec <mojca at macports dot org> ---
In the meantime I realized that the part of our build system that supports
compiling cross-tools does the following:
---> Extracting gcc-6.2.0.tar.bz2
---> Patching cpp.texi: s|setfilename cpp.info|setfilename
x86_64-w64-mingw32-cpp.info|g
---> Patching cpp.texi: s|(cpp)|(x86_64-w64-mingw32-cpp)|g
---> Patching cpp.texi: s|@file{cpp}|@file{x86_64-w64-mingw32-cpp}|g
---> Patching Makefile.in:
s:[[:<:]]cpp\.(info|pod|texi):x86_64-w64-mingw32-&:g
---> Patching Makefile.in:
s|--info-dir=$(DESTDIR)$(infodir)|--dir-file=$(DESTDIR)$(infodir)/x86_64-w64-mingw32-gcc-dir|g
---> Patching cppinternals.texi: s|setfilename cppinternals.info|setfilename
x86_64-w64-mingw32-cppinternals.info|g
---> Patching cppinternals.texi:
s|(cppinternals)|(x86_64-w64-mingw32-cppinternals)|g
---> Patching cppinternals.texi:
s|@file{cppinternals}|@file{x86_64-w64-mingw32-cppinternals}|g
---> Patching Makefile.in:
s:[[:<:]]cppinternals\.(info|pod|texi):x86_64-w64-mingw32-&:g
---> Patching Makefile.in:
s|--info-dir=$(DESTDIR)$(infodir)|--dir-file=$(DESTDIR)$(infodir)/x86_64-w64-mingw32-gcc-dir|g
---> Patching gcc.texi: s|setfilename gcc.info|setfilename
x86_64-w64-mingw32-gcc.info|g
---> Patching gcc.texi: s|(gcc)|(x86_64-w64-mingw32-gcc)|g
---> Patching gcc.texi: s|@file{gcc}|@file{x86_64-w64-mingw32-gcc}|g
---> Patching Makefile.in:
s:[[:<:]]gcc\.(info|pod|texi):x86_64-w64-mingw32-&:g
---> Patching Makefile.in:
s|--info-dir=$(DESTDIR)$(infodir)|--dir-file=$(DESTDIR)$(infodir)/x86_64-w64-mingw32-gcc-dir|g
---> Patching gccint.texi: s|setfilename gccint.info|setfilename
x86_64-w64-mingw32-gccint.info|g
---> Patching gccint.texi: s|(gccint)|(x86_64-w64-mingw32-gccint)|g
---> Patching gccint.texi: s|@file{gccint}|@file{x86_64-w64-mingw32-gccint}|g
---> Patching Makefile.in:
s:[[:<:]]gccint\.(info|pod|texi):x86_64-w64-mingw32-&:g
---> Patching Makefile.in:
s|--info-dir=$(DESTDIR)$(infodir)|--dir-file=$(DESTDIR)$(infodir)/x86_64-w64-mingw32-gcc-dir|g
---> Patching gccinstall.info: s|setfilename gccinstall.info|setfilename
x86_64-w64-mingw32-gccinstall.info|g
---> Patching gccinstall.info:
s|(gccinstall)|(x86_64-w64-mingw32-gccinstall)|g
---> Patching gccinstall.info:
s|@file{gccinstall}|@file{x86_64-w64-mingw32-gccinstall}|g
---> Patching Makefile.in:
s:[[:<:]]gccinstall\.(info|pod|info):x86_64-w64-mingw32-&:g
---> Patching Makefile.in:
s|--info-dir=$(DESTDIR)$(infodir)|--dir-file=$(DESTDIR)$(infodir)/x86_64-w64-mingw32-gcc-dir|g
---> Patching libquadmath.info: s|setfilename libquadmath.info|setfilename
x86_64-w64-mingw32-libquadmath.info|g
---> Patching libquadmath.info:
s|(libquadmath)|(x86_64-w64-mingw32-libquadmath)|g
---> Patching libquadmath.info:
s|@file{libquadmath}|@file{x86_64-w64-mingw32-libquadmath}|g
---> Patching Makefile.in:
s:[[:<:]]libquadmath\.(info|pod|info):x86_64-w64-mingw32-&:g
---> Patching Makefile.in:
s|--info-dir=$(DESTDIR)$(infodir)|--dir-file=$(DESTDIR)$(infodir)/x86_64-w64-mingw32-gcc-dir|g
---> Patching Makefile.in: /^install:/s/ .*//
---> Configuring x86_64-w64-mingw32-gcc-bootstrap
So maybe "proper" names of info files come from our build system after all and
nobody bothered ever testing the patches for fortran. I need to dig a bit
further.
It would of course be awesome if none of that patching was needed, but ...
