From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Michael Mishourovsky <mike.mishky@samsung.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Re: compiling gcc 5.x from the scratch: issues
Date: Thu, 10 Sep 2015 06:40:00 -0000 [thread overview]
Message-ID: <20150910064028.GD432@x4> (raw)
In-Reply-To: <1538298743.891721441863374462.JavaMail.weblogic@ep2mlwas03a>
On 2015.09.10 at 05:36 +0000, Michael Mishourovsky wrote:
> Dear Sirs, following your suggestions I checked again https://gcc.gnu.org/wiki/InstallingGCC.
>
> Key point was here: https://gcc.gnu.org/install/download.html (last
> passage) "Likewise the GMP, MPFR and MPC libraries can be
> automatically built together with GCC. Unpack the GMP, MPFR and/or MPC
> source distributions in the directory containing the GCC sources and
> rename their directories to gmp, mpfr and mpc, respectively (or use
> symbolic links with the same name)."
>
> Actually my assumption was that if I run download_prerequisites from
> /contrib, it will download everything and put it at right places; but
> actually it does not follow statement above (it does not create gmp,
> mpfr and mpc folder in main gcc package directory) So I did it
> manually and copied files there.
Well, https://gcc.gnu.org/wiki/InstallingGCC says:
»Alternatively, after extracting the GCC source archive, simply run the
./contrib/download_prerequisites script in the GCC source directory.«
The »in the GCC source directory« part is important. If you run it from
anywhere else it will not work.
--
Markus
next prev parent reply other threads:[~2015-09-10 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 5:36 Michael Mishourovsky
2015-09-10 6:40 ` Markus Trippelsdorf [this message]
2015-09-10 6:49 ` Markus Trippelsdorf
2015-09-10 16:23 ` Martin Sebor
2015-09-10 18:53 ` Jonathan Wakely
2015-09-10 19:15 ` Markus Trippelsdorf
2015-09-10 19:17 ` Jonathan Wakely
2015-09-11 1:38 Michael Mishourovsky
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=20150910064028.GD432@x4 \
--to=markus@trippelsdorf.de \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=mike.mishky@samsung.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).