From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: vicentesmith <vicentesmith@protonmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Components used to build GCC
Date: Tue, 8 Mar 2022 00:22:10 +0000 [thread overview]
Message-ID: <CAH6eHdTGetaBFiT393g--cQtBUt5FwJYunU5k5Wrozn4dxp41w@mail.gmail.com> (raw)
In-Reply-To: <gPUr-jSXUed3g62Su7pUaY9rS-bI9MvopadSNH7aIztAxVV7gRzVBRU-v1lqM9wSPXSCnSz15uRqO5gFK90wtC9S_OZanQhRj9CcCLobd90=@protonmail.com>
On Mon, 7 Mar 2022 at 22:27, vicentesmith via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Hello,
> I'm building GCC11 on a system running Ubuntu20.04 (that includes GCC 9.3.0). After downloading the prerequisites, the system is stating:
> ...
> gmp-6.1.0.tar.bz2: OK
> mpfr-3.1.6.tar.bz2: OK
> mpc-1.0.3.tar.gz: OK
> isl-0.18.tar.bz2: OK
> All prerequisites downloaded successfully.
> My question is whether the GCC build is going to use these versions of GMP, MPFR and MPC or the ones already installed in the system, which are more recent. Thanks.
When the sources are present in the GCC source tree (which is what the
download_prerequisites script does) then those ones will be used.
If you want to use the system versions, just remove the "gmp", "mpfr",
"mpc" and "isl" symlinks in the GCC source tree. You can also remove
the gmp-6.1.0, mpfr-3.1.6 etc. directories, but doing so isn't
necessary. The configure script only looks for the unversioned names,
so removing the symlinks is sufficient.
prev parent reply other threads:[~2022-03-08 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 22:26 vicentesmith
2022-03-08 0:22 ` Jonathan Wakely [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=CAH6eHdTGetaBFiT393g--cQtBUt5FwJYunU5k5Wrozn4dxp41w@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=vicentesmith@protonmail.com \
/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).