public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kirill Voronin" <kvoronin@labchem.sscc.ru>
To: gcc-help@gcc.gnu.org
Subject: Re: Re: Problem with building gcc 4.9.0 (libstdc++)
Date: Fri, 08 Aug 2014 11:13:00 -0000	[thread overview]
Message-ID: <3c0a74bf59884203f5d4ada056b31054.squirrel@mx.sscc.ru> (raw)
In-Reply-To: <CAH6eHdRCBcLyu3DrbVitc0=RUpQDOLM+4DWcCHaaSTZs_PsySA@mail.gmail.com>


OK, thanks for you responses.

Can you please make it a bit more clear about how to build gcc after using
download_prerequisites script ?

Running

 ../gcc-4.9.0/configure
--prefix=/ifs/home/icmmg/voronin/pardiso_proekt/pardiso_project/new/gcc_install
--enable-shared

fails with the error

checking for the correct version of gmp.h... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.

since there is no gmp, mpc and mpfr built.
As far as i understand, the download_prerequisites script just downloads
the source files.

How should I build it?


> On 8 August 2014 11:22, Kirill Voronin <kvoronin@labchem.sscc.ru> wrote:
>>
>> Actually, the version doesn't matter except it should be greater than
>> 4.8.
>>
>> I've already read
>>
>> https://gcc.gnu.org/wiki/FAQ#configure_suffix
>>
>> but actually there is no answer for my case since I do have mpc, gmp and
>> mpfr installed (correctly at least as make check claimed for each of
>> these
>> three).
>
> Then you failed to understand the FAQ. It does answer your case.
>
>> If it didn't find some libs, I understand that I would have checked the
>> option --with-... and check the paths but now it seems like installing
>> one
>> of the internal (for gcc) packages stdc++ failed.
>
> Wrong.
>
>> So, you recommend to install mpc, gmp and mpfr once again using
>> prerequisites?
>
> Don't install them separately if you don't know what you're doing.
>
> See http://gcc.gnu.org/wiki/InstallingGCC
>


-- 


  reply	other threads:[~2014-08-08 11:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  9:54 Kirill Voronin
2014-08-08  9:56 ` Jonathan Wakely
2014-08-08  9:58   ` Jonathan Wakely
2014-08-08 10:22     ` Kirill Voronin
2014-08-08 10:27       ` Jonathan Wakely
2014-08-08 11:13         ` Kirill Voronin [this message]
2014-08-08 11:33           ` Jonathan Wakely
2014-08-08 11:38             ` Jonathan Wakely
2014-08-10 11:58               ` Kirill Voronin
2014-08-10 17:43                 ` Jonathan Wakely
2014-08-10 12:24 ` Brian Drummond
2014-08-10 14:29   ` Kirill Voronin
2014-08-10 17:54     ` Jonathan Wakely

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=3c0a74bf59884203f5d4ada056b31054.squirrel@mx.sscc.ru \
    --to=kvoronin@labchem.sscc.ru \
    --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).