Re: Minimum GMP/MPFR version bumps for GCC-4.5

["Kaveh Ghazi" <kghazi at mekamail dot com>]

From: "Steven Bosscher" <stevenb.gcc@gmail.com>

> The problem doesn't happen on machines I own or have root access to.
> It's only a problem when you try to do gcc development on machines
> hosted by 3rd parties (SF compile farm, HP cluster, machines at places
> where I work and/or where I try to convince people to use gfortran
> instead of e.g. sunf90, etc.).

I've frequently been in those situations, especially evangelizing GCC on 
non-linux-gnu where you never have GMP/MPFR by default.   In that case you 
simply drop the necessary tarballs of GMP/MPFR in your GCC source dir and do 
an in-tree build of the whole lot.  For the MPC library integration, the 
patches I posted support in-tree builds for MPC as well.  So there's no loss 
of this workaround for the situation you described.

Anyway I think that's tangential to the topic at hand, this isn't really the 
MPC thread.  Here's it's only whether it's okay (i.e. low disruption) to 
upgrade to gmp-4.2 (three year old release) and mpfr-2.3.1 (a micro bump 
above what we require now).  Based on my own observations and what othes 
have said here, it seems to me that either you already have the necessary 
versions supplied by your distro, or you've already had to go through the 
trouble of getting a recent release.  I haven't heard of anyone who would 
have previously gotten the software by default and would now have to do an 
extra manual step.  Even if there were, it's not such a big deal IMHO to get 
the packages and drop them in your gcc sources.

       --Kaveh