https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69129
--- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> --- rechecked with today's trunk on Debian unstable, reproduced. The compiler is configured with: configure -v --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm --disable-libsanitizer --disable-libquadmath --enable-plugin --with-system-zlib --enable-multiarch --enable-multilib --with-arch-32=mips32r2 --with-fp-32=xx --enable-targets=all --with-arch-64=mips64r2 --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=mips-linux-gnu --program-prefix=mips-linux-gnu- --includedir=/usr/mips-linux-gnu/include according to https://buildd.debian.org/status/logs.php?pkg=gcc-snapshot&arch=mipsel the libgfortran failure is first seen with trunk 20150722 in native builds.