From: Nils Pipenbrinck <n.pipenbrinck@cubic.org>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Antwort: Re: Antwort: Re: [PATCH]: bump minimum MPFR version, (includes some fortranbits)
Date: Tue, 14 Oct 2008 22:29:00 -0000 [thread overview]
Message-ID: <48F500F9.1080509@cubic.org> (raw)
In-Reply-To: <OFC84C70D0.DFCC377F-ONC12574E2.0042BFBE-C12574E2.00441902@AT.TOP.COM>
Markus Milleder wrote:
> I don't think anybody who tries to build GCC from source will have any
> problem building MPFR first.
>
Not entirely true:
Those of us who use cygwin and want to use the latest GCC have to first
compile a non MPFR GCC (e.g. 4.1.x) before they can compile the latest
GPFR and link GCC to it.
This is not a big deal if you know that you have to do that, but if you
don't know why the MPFR fails and wich snapshot you have to use as an
immediate step it can be very frustrating.
I would welcome a configuration option that disables all the MPFR
related things. That would make compiling GCC on a naked cygwin
installation *much* easier.
Cheers,
Nils Pipenbrinck
next prev parent reply other threads:[~2008-10-14 20:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 5:56 [PATCH]: bump minimum MPFR version, (includes some fortran bits) Kaveh R. GHAZI
2008-10-05 13:52 ` Richard Guenther
2008-10-05 14:10 ` Gerald Pfeifer
2008-10-05 14:43 ` Richard Guenther
2008-10-05 16:34 ` Manuel López-Ibáñez
2008-10-06 23:37 ` Kaveh R. Ghazi
2008-10-07 7:55 ` Janne Blomqvist
2008-10-06 13:56 ` Adrian Bunk
2008-10-06 23:16 ` [PATCH]: bump minimum MPFR version, (includes some fortranbits) Kaveh R. Ghazi
2008-10-06 23:40 ` Ben Elliston
2008-10-07 0:35 ` Andrew Pinski
2008-10-07 18:52 ` Adrian Bunk
2008-10-13 16:00 ` Vincent Lefevre
2008-10-13 16:42 ` Antwort: " Markus Milleder
2008-10-13 17:15 ` Adrian Bunk
2008-10-14 12:59 ` Antwort: " Markus Milleder
2008-10-14 13:10 ` Jakub Jelinek
2008-10-14 13:21 ` Tobias Schlüter
2008-10-14 14:52 ` Adrian Bunk
2008-10-14 15:39 ` Tobias Schlüter
2008-10-14 13:30 ` Antwort: Re: Antwort: " Adrian Bunk
2008-10-14 22:29 ` Nils Pipenbrinck [this message]
2008-10-14 22:31 ` Andrew Pinski
2008-10-15 0:59 ` Nils Pipenbrinck
2008-10-15 1:01 ` Andrew Pinski
2008-10-15 10:56 ` Brian Dessent
2008-10-15 1:09 ` Dave Korn
2008-10-26 12:59 ` [PATCH]: bump minimum MPFR version, (includes some fortran bits) Geoff Keating
2008-10-26 14:42 ` Jakub Jelinek
2008-10-27 2:50 ` Kaveh R. Ghazi
2008-10-27 7:03 ` David Edelsohn
2008-10-27 15:03 ` Joseph S. Myers
2008-10-27 15:14 ` Richard Guenther
2008-10-27 16:53 ` Joseph S. Myers
2008-10-27 20:34 ` Roberto Bagnara
2008-10-27 16:17 ` David Edelsohn
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=48F500F9.1080509@cubic.org \
--to=n.pipenbrinck@cubic.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).