From: "Adrian Bunk" <[EMAIL PROTECTED]>
On Sat, Oct 04, 2008 at 09:33:48PM -0400, Kaveh R. GHAZI wrote:
Since we're in stage3, I'm raising the issue of the MPFR version we
require for GCC, just as in last year's stage3 for gcc-4.3:
http://gcc.gnu.org/ml/gcc/2007-12/msg00298.html
I'd like to increase the "minimum" MPFR version to 2.3.0, (which has been
released since Aug 2007). The "recommended" version of MPFR can be
bumped
to the latest which is 2.3.2.
...
Considering that your patch removes the conditionals on MPFR versions
from the code (good!), is there any reason for gcc to keep this unusual
minimum/recommended split in the requirement?
Either 2.3.0 is good enough, or 2.3.2 contains some critical fix
and should be the minimum version.
The last time this came up, the consensus was that we should not hard fail
the configure script even if the user would then be missing some mpfr bugfix
in the latest/greatest release. That's why we have the minimum/recommended
split.
But I see no reason not to encourage people and/or make them aware of the
need to upgrade if they are so inclined. Whether a particular fix is
"critical" can be in the eye of the beholder.
--Kaveh
