This is the mail archive of the
mailing list for the GCC project.
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: Andrew Haley <aph at redhat dot com>
- To: Tom Browder <tom dot browder at gmail dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sat, 28 Aug 2010 13:04:37 +0100
- Subject: 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> <4C77AAF0.firstname.lastname@example.org> <AANLkTi=wYLVW1hab8tuV=HmWQA2A8ARe3iaAkVzPi-Jj@mail.gmail.com> <4C77AEE0.email@example.com> <AANLkTim=csN=nipeys22wqUaM0S-kQfg5dT6Qj0t5-oD@mail.gmail.com> <4C77C8F5.firstname.lastname@example.org> <AANLkTinoDe7g4-CNa6+bALE0JWwYayFbFF8nw-dx16Ab@mail.gmail.com> <AANLkTi=e0d5qFHU6wQ2jx2F0bSmBYaQuYwb_z6=4vTxt@mail.gmail.com>
[ Redirect to gcc. This is a dev issue. ]
On 08/27/2010 10:39 PM, Tom Browder wrote:
>> On Fri, Aug 27, 2010 at 09:17, Andrew Haley <email@example.com> wrote:
>>> However, just running download_prerequisites is, IMVHO, the only sane way
>>> to do it.
> That's the solution I used, and I got a good build--thanks for the tip, Andrew.
> I think what we have here is a gcc dependence on specific versions of
> gmp, mpfr, and mpc--more than is indicated in the installation
> instructions. I have used later versions of all of them and they
> cause interdependency problems of all sorts with later rerequisites.
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.
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