This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Including GMP/MPFR in GCC repository?
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: "Kaveh R. GHAZI" <ghazi at caip dot rutgers dot edu>
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, fortran at gcc dot gnu dot org, paul at codesourcery dot com, kargl at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 12 Oct 2006 11:50:52 -0700
- Subject: Re: Including GMP/MPFR in GCC repository?
- References: <Pine.GSO.4.58.0610062205240.2597@caipclassic.rutgers.edu> <452B11F1.8060406@codesourcery.com> <Pine.GSO.4.58.0610112313340.933@caipclassic.rutgers.edu> <20061012053416.GA5111@troutmask.apl.washington.edu> <Pine.GSO.4.58.0610121401520.7159@caipclassic.rutgers.edu>
On Thu, Oct 12, 2006 at 02:14:53PM -0400, Kaveh R. GHAZI wrote:
> On Wed, 11 Oct 2006, Steve Kargl wrote:
> >
> > It should be straight forward to modify the current configure tests
> > in toplevel for the versions of gmp and mpfr you need. I would
> > recommend at least mpfr 2.2.0 (which would allow me to kill the ugly
> > hacks in gfortran). For gmp, you may be able to use a version as
> > old as 4.1.0.
>
> Like this? I combined the two MPFR tests into one and had it stop if
> configure can't find the right versions of the libraries.
>
> Tested on sparc-sun-solaris2.10 via "configure" with no GMP/MPFR, with an
> older MPFR version and with current versions. It did the "right thing" in
> all cases.
>
> Okay for stage1?
>
The patch looks okay to me, but you'll need one of the
build machinery people to approve the patch.
--
Steve