This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
checking whether the GNU Fortran compiler is working... no
configure: error: GNU Fortran is not working; please report a bug in
http://gcc.gnu.org/bugzilla, attaching
/home/fxcoudert/svn/debug3/ibin/i686-pc-linux-gnu/libgfortran/ config.log
Perhaps we can tell the user to first look into the failure? The error
message could mention a few hints about GMP and MFPR too.
Bootstrapped and tested on i686-linux. OK for mainline? Would it be OK
to backport this to 4.2, a few weeks after it has been commited to
mainline? (I think it's an annoying bug for users compiling on unusual
platforms or using unusual configurations).
unusual == non-Linux I presume? Solaris is definitely not unusual. I'd second putting this on the 4.2 branch, rather sooner than later.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |