This is the mail archive of the
mailing list for the GCC project.
Re: Problems with upstream versions of gmp, mpfr, and mpc [Was: Bug in Build System of gcc-4.5.1? Cannot Find libmpc.so.2]
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, Tom Browder <tom dot browder at gmail dot com>
- Date: Sat, 28 Aug 2010 18:45:30 +0200
- Subject: Re: Problems with upstream versions of gmp, mpfr, and mpc [Was: Bug in Build System of gcc-4.5.1? Cannot Find libmpc.so.2]
- References: <AANLkTin-H27VhD-=vifhor-SD53xh+qEVp8pdanuQEt1@mail.gmail.com> <AANLkTi=e0d5qFHU6wQ2jx2F0bSmBYaQuYwb_z6=4vTxt@mail.gmail.com> <4C78FB55.email@example.com>
> I'm very sceptical about "or any later version" instructions when
> building the gcc prerequisites. In practice this can never be certain
> to work, because the upstream maintainers of these tools can change
> them in ways that break gcc.
Indeed, on the SPARC we seem to have problems (miscompilations: fortran/45277,
target/45363, c/45407) with any newer versions of GMP/MPFR/MPC. So I'm going
to add a blurb to the platform-specific instructions about that.
> Somehow, we need to keep an eye on these issues so that if a new
> version of a library changes in a way that breaks the gcc build we
> notice. But I don't think we have any mechanism to do that at
Yes, I think we should have recommended versions for the 3rd party libraries.