From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Kirill Voronin <kvoronin@labchem.sscc.ru>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Problem with building gcc 4.9.0 (libstdc++)
Date: Fri, 08 Aug 2014 09:58:00 -0000 [thread overview]
Message-ID: <CAH6eHdRuhRFpW8Niky8-KTOuDD5tjqrk1cwXQtDXsoLNeRxkMg@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRoGbAQw-rEaikyeYoUC_apLc-=eVi2_FEgb9Zx3iUaiQ@mail.gmail.com>
On 8 August 2014 10:56, Jonathan Wakely wrote:
> On 8 August 2014 10:54, Kirill Voronin wrote:
>>
>> I'm trying to build gcc 4.9.0 for linux (OS Red Hat, very old version).
Also, any reason why you are not using 4.9.1 instead?
>> I've installed manually mpc, gmp and mpfr before running ./configure
>>
>> Configure line:
>> ../gcc-4.9.0/configure --prefix=/usr/new/gcc_install --enable-shared
>> --with-gmp=/usr/new/gmp_install --with-mpfr=/usr/new/mpfc_install
>> --with-mpc=/usr/new/mpc_install
>>
>> and it works fine.
>>
>> But then I tried to make and got the following error:
>>
>> checking for suffix of object files... configure: error: in
>> `/ifs/home/icmmg/voronin/pardiso_proekt/pardiso_project/new/gcc_dir/x86_64-unknown-linux-gnu/libgcc':
>> configure: error: cannot compute suffix of object files: cannot compile
>
> https://gcc.gnu.org/wiki/FAQ#configure_suffix
>
> Follow http://gcc.gnu.org/wiki/InstallingGCC
Specifically, do not install GMP, MPFR and MPC separately, use the
download_prerequisites script.
next prev parent reply other threads:[~2014-08-08 9:58 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 [this message]
2014-08-08 10:22 ` Kirill Voronin
2014-08-08 10:27 ` Jonathan Wakely
2014-08-08 11:13 ` Kirill Voronin
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=CAH6eHdRuhRFpW8Niky8-KTOuDD5tjqrk1cwXQtDXsoLNeRxkMg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kvoronin@labchem.sscc.ru \
/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).