From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: ron.stubbs@duke.edu
Cc: gcc-help@gcc.gnu.org
Subject: Re: Configuration Error
Date: Wed, 15 Aug 2012 15:43:00 -0000 [thread overview]
Message-ID: <CAH6eHdRgkygwWnFhzi_PyQwy9gMjN6gtLx-qkD+6BGmwrGVc6w@mail.gmail.com> (raw)
In-Reply-To: <502B9888.4070205@duke.edu>
On 15 August 2012 13:39, Ron Stubbs wrote:
> Hi,
>
> I get the following configuration error message when configuring GCC 4.8
> on an x86_64 suystem running Scientific linux 6.2.
>
> checking for the correct version of gmp.h... yes
> checking for the correct version of mpfr.h... yes
> checking for the correct version of mpc.h... yes
> checking for the correct version of the gmp/mpfr/mpc libraries... 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
>
> Although the version check for the .h files succeeds, the library check
> fails.
>
> The installed version are required libraries:
> gmp-4.3.1-7.el6_2.2.x86_64
> mpfr-2.4.1-6.el6.x86_64
> mpc-0.8.2
>
> I've tried with both ./configure and /configure --with-gmp=/usr/lib64
> --with-mpfr=/usr/lib64 --with-mpc=/usr/local/lib
1) Don't use ./configure, as documented at
http://gcc.gnu.org/install/configure.html and
http://gcc.gnu.org/wiki/FAQ#configure and
http://gcc.gnu.org/wiki/InstallingGCC you should build outside the
source directory.
2) /usr/lib64 is a library path, not the installation prefix. You
would want to use --with-gmp-lib=/usr/lib64 or --with-gmp=/usr but the
compiler will always look in /usr/lib64 anyway so you shouldn't need
to use any --with-xxx options for gmp, mpfr and mpc if they're
installed in /usr
For more specific information on what fails you will need to look in
the config.log file.
next prev parent reply other threads:[~2012-08-15 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 14:34 Ron Stubbs
2012-08-15 15:43 ` Jonathan Wakely [this message]
2012-08-15 17:49 ` B B
2012-08-15 17:57 ` Jonathan Wakely
2012-08-15 18:03 ` Compilation Error Ron Stubbs
2012-08-15 18:14 ` Marc Glisse
2012-08-15 18:46 ` B B
[not found] ` <CAH6eHdRV5NLCO-+iJw1FHqw+6EV-LSCNkhF-SJ0jZUPtdbwFKQ@mail.gmail.com>
2012-08-15 19:25 ` Jonathan Wakely
2012-08-15 19:36 ` Ron Stubbs
2012-08-16 3:59 ` Marc Glisse
2012-08-16 13:29 ` Ron Stubbs
2012-08-16 15:15 ` Tim Prince
2012-08-16 20:06 ` Marc Glisse
2012-08-17 0:12 ` Ron Stubbs
2012-08-17 7:23 ` Marc Glisse
2012-08-17 8:23 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2001-01-20 22:50 configuration error Jeffery Zhang
2001-01-21 13:16 ` Alexandre Oliva
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=CAH6eHdRgkygwWnFhzi_PyQwy9gMjN6gtLx-qkD+6BGmwrGVc6w@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ron.stubbs@duke.edu \
/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).