public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Denis dot Excoffier at airbus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44455]  New: GCC fails to build if MPFR 3.0.0 (Release Candidate) is used
Date: Mon, 07 Jun 2010 20:42:00 -0000	[thread overview]
Message-ID: <bug-44455-12787@http.gcc.gnu.org/bugzilla/> (raw)

I have compiled sucessfully GCC 4.5.0 under various systems (solaris, cygwin,
darwin), using gmp-5.0.1, mpfr-2.4.2 and mpc-0.8.2 installed in the source tree
before compilation.

I've tried recently a new MPFR Release Candidate 2 (from
http://www.mpfr.org/mpfr-3.0.0/mpfr-3.0.0-rc2.tar.bz2) as a replacement for
mpfr-2.4.2.tar.bz2.

But It failed within stage 1 of mpfr, at least under darwin and solaris, with
the following message:

"header files gmp-impl.h and longlong.h not found"

It seems:
- that GCC compiles mpfr by passing the --with-gmp-build option to its
configure,
- that the new mpfr-3.0.0 now detects that the directory given under
--with-gmp-build does not contain the necessary files and aborts in this case
- that the same detection was performed under mpfr-2.4.2, albeit with no abort
- the two missing header files are present in the source directory, but not in
the build directory (the one given to --with-gmp-build)

I then tried to patch the mpfr/configure in order to skip this test (and the
following one "checking for valid GMP_NUMB_BITS"), and it seems to work: GCC is
built, and i can use this GCC like before. However i cannot say whether the
MPFR part is fully functioning or not.

See also http://websympa.loria.fr/wwsympa/arc/mpfr/2010-06/msg00003.html (the
french part of this message is summarized above). According to MPFR people, the
bug would reside in GCC.

Hope this helps (the future).

NB. I categorized this problem as more severe as "Normal", since it is likely
to affect many targets, and also affect all users that would want to upgrade
(blindly) to the last MPFR (within the GCC source directory).


-- 
           Summary: GCC fails to build if MPFR 3.0.0 (Release Candidate) is
                    used
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Denis dot Excoffier at airbus dot com


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


             reply	other threads:[~2010-06-07 20:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 20:42 Denis dot Excoffier at airbus dot com [this message]
2010-06-11  8:05 ` [Bug bootstrap/44455] " Denis dot Excoffier at airbus dot com
2010-06-14 17:35 ` nightstrike at gmail dot com
2010-06-14 17:51 ` froydnj at gcc dot gnu dot org
2010-07-07  7:45 ` marc dot glisse at normalesup dot org
2010-07-08 16:24 ` bonzini at gnu dot org
2010-07-11 11:18 ` a dot heider at gmail dot com
2010-07-12 20:34 ` marc dot glisse at normalesup dot org
2010-07-13  9:33 ` bonzini at gnu dot org
2010-07-13 14:26 ` marc dot glisse at normalesup dot org
2010-07-13 14:43 ` bonzini at gnu dot org
2010-07-13 15:01 ` marc dot glisse at normalesup dot org
2010-07-13 15:31 ` bonzini at gnu dot org
2010-07-23 19:35 ` rguenth at gcc dot gnu dot org
2010-07-23 19:35 ` rguenth 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-44455-12787@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).