public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/30753]  New: checking for correct version of gmp.h... no
Date: Sat, 10 Feb 2007 00:31:00 -0000	[thread overview]
Message-ID: <bug-30753-276@http.gcc.gnu.org/bugzilla/> (raw)

checking for correct version of gmp.h... no
configure: error: Building GCC requires GMP 4.1+ and MPFR 2.2.1+.
Try the --with-gmp and/or --with-mpfr options to specify their locations.
Copies of these libraries' source code can be found at their respective
hosting sites as well as at ftp://gcc.gnu.org/pub/gcc/infrastructure/.
See also http://gcc.gnu.org/install/prerequisites.html for additional info.
If you obtained GMP and/or MPFR from a vendor distribution package, make
sure that you have installed both the libraries and the header files.
They may be located in separate packages.

dave@hiauly6:~/gnu/gcc-4.3/objdir$ dpkg -l 'libgmp*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
pn  libgmp-ocaml   <none>         (no description available)
pn  libgmp-ocaml-d <none>         (no description available)
un  libgmp2        <none>         (no description available)
un  libgmp2-dev    <none>         (no description available)
pn  libgmp3        <none>         (no description available)
ii  libgmp3-dev    4.2.1+dfsg-4   Multiprecision arithmetic library developers
ii  libgmp3-doc    4.2.1+dfsg-4   Multiprecision arithmetic library example co
ii  libgmp3c2      4.2.1+dfsg-4   Multiprecision arithmetic library
pn  libgmpxx3      <none>         (no description available)
ii  libgmpxx4      4.2.1+dfsg-4   Multiprecision arithmetic library (C++ bindi

dave@hiauly6:~/gnu/gcc-4.3/gcc$ cat LAST_UPDATED
Fri Feb  9 19:18:57 EST 2007
Sat Feb 10 00:18:57 UTC 2007 (revision 121786)


-- 
           Summary: checking for correct version of gmp.h... no
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
 GCC build triplet: hppa-unknown-linux-gnu
  GCC host triplet: hppa-unknown-linux-gnu
GCC target triplet: hppa-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30753


             reply	other threads:[~2007-02-10  0:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10  0:31 danglin at gcc dot gnu dot org [this message]
2007-02-10  0:38 ` [Bug bootstrap/30753] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-02-10  0:42 ` drow at gcc dot gnu dot org
2007-02-10  0:53 ` dave at hiauly1 dot hia dot nrc dot ca
2007-02-10  1:01 ` drow at gcc dot gnu dot org
2007-02-10  1:17 ` dave at hiauly1 dot hia dot nrc dot ca
2007-02-10  1:37 ` drow at gcc dot gnu dot org
2007-02-10  1:53 ` dave at hiauly1 dot hia dot nrc dot ca
2007-02-13 13:40 ` drow at gcc dot gnu dot org
2007-02-13 13:40 ` drow at gcc dot gnu dot org

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=bug-30753-276@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).