From: "Smith-Rowland, Edward M" <ESmith-rowland@alionscience.com>
To: <gcc-help@gcc.gnu.org>
Subject: Building gcc on X86_64
Date: Fri, 17 Nov 2006 17:28:00 -0000 [thread overview]
Message-ID: <893D428105AB9F49AC7A5C96A454A8B8138C0E@email4a.alionscience.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
I'm trying to bootstrap gcc on x86_64.
Here is my configure line:
../gcc/configure --prefix=/home/ed/bin-4.3 --enable-languages=c,c++,fortran --with-gmp-dir=/home/ed/gcc/gmp-4.2.1 --with-mpfr-dir=/home/ed/gcc/mpfr-2.2.0
I just unpacked the GMP and MPFR source directories in the gcc source tree.
My question is why does the configure check require the mpfr library to already be built when I put two source directories? It seems like it should just check the headers. Then it should configure and build those packages using the most useful flags for GCC.
Ed
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: config.log --]
[-- Type: text/x-log; name="config.log", Size: 1594 bytes --]
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:614: checking host system type
configure:635: checking target system type
configure:653: checking build system type
configure:708: checking for a BSD compatible install
configure:761: checking whether ln works
configure:785: checking whether ln -s works
configure:1850: checking for gcc
configure:1963: checking whether the C compiler (gcc ) works
configure:1979: gcc -o conftest conftest.c 1>&5
configure:2005: checking whether the C compiler (gcc ) is a cross-compiler
configure:2010: checking whether we are using GNU C
configure:2019: gcc -E conftest.c
configure:2038: checking whether gcc accepts -g
configure:2105: checking for gnatbind
configure:2170: checking whether compiler driver understands Ada
configure:2202: checking how to compare bootstrapped objects
configure:2300: checking for correct version of gmp.h
configure:2313: gcc -c -g -O2 -I/home/ed/gcc/mpfr-2.2.0 -I/home/ed/gcc/gmp-4.2.1 conftest.c 1>&5
configure:2328: checking for correct version of mpfr.h
configure:2343: gcc -o conftest -g -O2 -I/home/ed/gcc/mpfr-2.2.0 -I/home/ed/gcc/gmp-4.2.1 conftest.c /home/ed/gcc/mpfr-2.2.0/libmpfr.a 1>&5
gcc: /home/ed/gcc/mpfr-2.2.0/libmpfr.a: No such file or directory
configure: failed program was:
#line 2330 "configure"
#include "confdefs.h"
#include <gmp.h>
#include <mpfr.h>
int main() {
#if MPFR_VERSION_MAJOR < 2 || (MPFR_VERSION_MAJOR == 2 && MPFR_VERSION_MINOR < 2)
choke me
#endif
mpfr_t n; mpfr_init(n);
; return 0; }
next reply other threads:[~2006-11-17 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 17:28 Smith-Rowland, Edward M [this message]
2009-03-15 16:22 Building gcc on x86_64 Revital1 Eres
2009-03-19 14:21 Sergei Dyshel
2009-03-19 14:26 ` John (Eljay) Love-Jensen
2009-03-19 14:38 ` Sergei Dyshel
2009-03-19 23:22 ` Ian Lance Taylor
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=893D428105AB9F49AC7A5C96A454A8B8138C0E@email4a.alionscience.com \
--to=esmith-rowland@alionscience.com \
--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).