Re: [PING][PATCH]: Warn that mpfr-2.2.0 is buggy when configuring

[Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>]

> > 2006-12-17  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
> >
> > 	* configure.in: Warn that MPFR 2.2.0 is buggy.
> >
> > 	* configure: Regenerate.
>
> PING for configure patch.
>
> http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01249.html

I disagree with Joe on this: I think that we should not accept MPFR 
2.2.1 because, by the time GCC 4.3 is out, most distros will have 
upgraded to the new version.  The comparison with binutils is "unfair" 
because gcc's configure script has code to detect some known binutils 
deficiencies or bugs, and will omit features in case the detected 
version is buggy.  So, unless we do the same for MPFR (not in GCC's 
configure script: we may just disable MPFR constant folding if the 
version is 2.2.0), there is no reason to allow a buggy version of a 
library that GCC has not ever required (at least for the C/C++ front-ends).

The patch is ok for the 4.2 branch, modulo changing "buggy version" with 
"yes, buggy but acceptable", because we don't use the buggy features in 
that branch.

For mainline, however, since I am a new maintainer I will just defer to 
people more experienced than me.

Paolo