From: Ron Zamir <zamir.ron@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: errors building gcc-10.2
Date: Tue, 11 Aug 2020 03:01:12 +0300 [thread overview]
Message-ID: <CAORg4NJEazz9xLpbjHbspirW6HhfWR5Z2cepnB2cBFuxnpae-A@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVab0UAqQ8dRF6+YcFBh6HaLg2yA9JypJzHhm_0xRTdQEow@mail.gmail.com>
Problem solved
1. Instead of the latest and greatest versions of the libraries (mpc, gmp,
mpfr, isl) I used the download_prerequisites script in contrib
2. I used a gcc 8 binary
gcc 10.2 built successfully
Thanks
בתאריך יום ג׳, 11 באוג׳ 2020, 02:53, מאת Jim Wilson <jimw@sifive.com>:
> On Sun, Aug 9, 2020 at 6:01 PM Ron Zamir via Gcc-help
> <gcc-help@gcc.gnu.org> wrote:
> > trying to build gcc-10.2
> > I've added the latest sources for the GMP, MPFR, MPC, ISL libraries
> > My system is CentOS 7.8 with gcc version 4.85
>
> gcc-4.8.5 is rather old. I'd suggest installing a more recent version
> of gcc using the software collections web site.
>
> https://wiki.centos.org/AdditionalResources/Repositories/SCL
> https://www.softwarecollections.org/en/scls/rhscl/devtoolset-8/
>
> Looks like gcc-8 is the most recent one that they have, but using
> gcc-8 to build gcc-10 will likely work much better than using
> gcc-4.8.5 to build gcc-10. Adding the devtoolset-8 also gets you more
> recent versions of gmp, mpfr, and mpc, which might be recent enough to
> make the gcc-10 build happy.
>
> Jim
>
prev parent reply other threads:[~2020-08-11 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 1:01 Ron Zamir
2020-08-10 6:44 ` Marc Glisse
2020-08-10 23:53 ` Jim Wilson
2020-08-11 0:01 ` Ron Zamir [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAORg4NJEazz9xLpbjHbspirW6HhfWR5Z2cepnB2cBFuxnpae-A@mail.gmail.com \
--to=zamir.ron@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).