https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
Mojca Miklavec changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
--- Comment #3 from Mojca Miklavec ---
And just for the reference, here's the commit that fixed the behaviour for us:
https://github.com/macports/macports-ports/commit/0b41554b5c627dcd5d095b1b432f554993df4c90
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
--- Comment #2 from Mojca Miklavec ---
I just wanted to confirm that doing the same kind of replacement for gfortran
as our package manager does for gcc, I get the expected result. So gfortran's
info file doesn't seem to behave any different from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
--- Comment #1 from Mojca Miklavec ---
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|setfil
