public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc@Denis-Excoffier.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50461] New: mpfr.h found in mpfr-3.1.0/src instead of mpfr-3.0.1/. as previously
Date: Tue, 20 Sep 2011 09:01:00 -0000	[thread overview]
Message-ID: <bug-50461-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50461
           Summary: mpfr.h found in mpfr-3.1.0/src instead of mpfr-3.0.1/.
                    as previously
    Classification: Unclassified
           Product: gcc
           Version: 4.6.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gcc@Denis-Excoffier.org


Hi,

I bootstrap gcc-4.6.1 by installing the gmp/, mpfr/ and mpc/ folders directly
in the GCC source tree as suggested in the installation notes.

Yesterday, they created a new mpfr-3.1.0-rc1 as a replacement for mpfc-3.0.1 we
used to have before. Now, with this new mpfr, the bootstrap fails at the step:
"Configuring mpc at stage 1".

Solution:
Compared to mpfr-3.0.1, the new mpfr-3.1.0-rc1 has an additional src folder.
Therefore, the ./configure of GCC has to be modified, eg by replacing (sed
syntax):

s|$$s/mpfr|&/src|g         (1 occurrence)
and
s|$$r/$(HOST_SUBDIR)/mpfr|&/src|g      (2 occurrences)

With this modification, everything works fine. I don't think that the MPFR
people will remove the src folder in the next future. I suppose this is for all
platforms, in any case at least Linux Ubuntu and Darwin Leopard.

Regards,

Denis Excoffier.


             reply	other threads:[~2011-09-20  8:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  9:01 gcc@Denis-Excoffier.org [this message]
2011-09-22  6:42 ` [Bug bootstrap/50461] " gcc@Denis-Excoffier.org
2011-10-04  7:07 ` gcc@Denis-Excoffier.org
2011-10-04  9:01 ` redi at gcc dot gnu.org
2012-01-21 18:21 ` psmith at gnu dot org
2012-01-21 18:29 ` pinskia at gcc dot gnu.org
2012-05-09 16:23 ` nickc at gcc dot gnu.org
2012-07-25 19:41 ` nightstrike at gmail dot com
2012-08-23 15:26 ` redi at gcc dot gnu.org
2012-08-23 15:44 ` redi at gcc dot gnu.org
2012-09-21 17:17 ` karl at freefriends dot org
2012-10-07 21:28 ` eyurtese at abo dot fi
2012-10-08  9:51 ` redi at gcc dot gnu.org
2012-10-08 12:17 ` eyurtese at abo dot fi
2012-10-08 12:22 ` redi at gcc dot gnu.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-50461-4@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).