This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.9.2 Build Fails at cc1
- From: Cyd Haselton <chaselton at gmail dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Mon, 8 Dec 2014 10:06:47 -0600
- Subject: Re: GCC 4.9.2 Build Fails at cc1
- Authentication-results: sourceware.org; auth=none
- References: <CAHu5PraGXAt==5gN8F8akrVg+14a56ycORgMmKXh0VOVAdZWCw at mail dot gmail dot com> <547F5278 dot 90906 at redhat dot com> <CAHu5Prb=G7Kvh5mSOe2oe6wKwBFwQcxPF_dhPdWH-E+AzbhwfA at mail dot gmail dot com> <54802DEC dot 8000403 at redhat dot com> <CAHu5PrZMu7akRSgY+z_ZzQO8WAWUBcq1qzm2mwMcT91SKTFYuQ at mail dot gmail dot com> <548063CF dot 9070100 at redhat dot com> <CAHu5PrYJ_uNew7_dkDhtUovm8uNHF3aSnBvpSBwFqE-xyNLWWQ at mail dot gmail dot com> <54809118 dot 90601 at redhat dot com> <CAHu5PrYYFSQuyU=5CDObMwyphj1eAdykPymt5n20AM4bUUSUzQ at mail dot gmail dot com> <54809A96 dot 2020300 at redhat dot com> <CAHu5Prb-3pAkpR93+TWsB0J2STU_3-XUYXO3Um87cty1uMnYKw at mail dot gmail dot com> <5480E7CB dot 4010302 at redhat dot com> <CAHu5Pra7kBjw_EgY9i5GGaogvedhZAf_ouRHZWC8j89QREob8Q at mail dot gmail dot com> <54817C09 dot 9010603 at redhat dot com> <CAHu5PrbkPiECgo9=tLD8dxe0+Z0jjbXMBff5z19TiJfRhNKXKg at mail dot gmail dot com> <alpine dot DEB dot 2 dot 11 dot 1412061921360 dot 14163 at laptop-mg dot saclay dot inria dot fr> <548576F4 dot 6030604 at redhat dot com> <CAHu5PrYt4TROxtcFNG2eyo93Cr4-Z3f85yVifKOYs=0wnP9mAg at mail dot gmail dot com> <alpine dot DEB dot 2 dot 11 dot 1412081510000 dot 1566 at laptop-mg dot saclay dot inria dot fr> <CAHu5PrZ5TR5sjuAD2QsQyW+vQwBDysh13p8iE7O_qbdfYz8EWA at mail dot gmail dot com> <CAH6eHdQrAPNdkLsZyBT+cUmnFvuWRCk+G7ShQwBAa4Wu-i5CGg at mail dot gmail dot com>
On Mon, Dec 8, 2014 at 10:02 AM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 8 December 2014 at 14:31, Cyd Haselton wrote:
>> Because there's a balance between later stable version and later
>> version that works with an in-tree build of GCC/MPFR/MPC.
>> My reasoning was that 5.0.0 is the next version up from 4.3.2...which
>> is the version specified in download_prerequisites...but that was
>> before finding out that version 5.0.0 introduced a bunch of new code.
>
> But if there are bugs introduced in the jump from 4.y.z to the new
> major release 5.0.0 then they will be fixed in 5.0.1, and even more
> will be fixed in 5.0.2, and so on.
>
> In general 5.0.1 will not introduce any new features since 5.0.0, it
> will only stabilise it and fix bugs. The same applies to GCC releases.
> So your reasoning that keeps leading you to x.y.0 releases is
> seriously flawed. x.y.0 is invariably the worst of all x.y.z releases.
I believe I understand now. So, if the latest stable version of gmp
is 6.0.0, I should either go with 5.0.z, 4.3.2 or wait for the next
bugfix?
And, if I move to a newer version of GMP...either 5.0.z or 6.0.x,
which version of mpfr/mpc do I move to...i.e. is there a chart or
grid?