From: rridge@csclub.uwaterloo.ca (Ross Ridge)
To: Mark Mitchell <mark@codesourcery.com>
Cc: Ross Ridge <rridge@csclub.uwaterloo.ca>,
DJ Delorie <dj@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32
Date: Fri, 22 Jul 2005 20:15:00 -0000 [thread overview]
Message-ID: <20050722201547.DE1D3A8595@perpugilliam.csclub.uwaterloo.ca> (raw)
In-Reply-To: <42E13C29.2030708@codesourcery.com>
Ross Ridge wrote:
>I don't see how the existance of configure changes the fact the GCC
>compiler driver exists,
DJ Delorie wrote:
>At the time you're running configure, the gcc driver does *not* exist,
>but you *do* need to run as and ld to test what features they support,
>information which is needed in order to *build* gcc.
Ross Ridge wrote:
> I don't see the relevence to problem at hand. The Makefile that contains
> the currect hack that's causing the problem doesn't exist at configure
> time either.
Mark Mitchell wrote:
> Right. The real solution is to separate libgcc from the rest of the
> compiler; you should be able to (a) use configure to detect features of
> your as/ld, (b) build the compiler, (c) install it, and, only then, (d)
> start building libraries.
Sorry, but I don't see the relevence of this either. Are you and DJ
Delorie trying to address some other problem then the fact that GCC
doesn't bootstrap on MinGW builds?
Ross Ridge
next prev parent reply other threads:[~2005-07-22 20:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 6:20 Ross Ridge
2005-07-21 16:19 ` DJ Delorie
2005-07-21 17:32 ` Ross Ridge
2005-07-21 17:48 ` DJ Delorie
2005-07-21 18:17 ` Ross Ridge
2005-07-22 18:34 ` Mark Mitchell
2005-07-22 20:15 ` Ross Ridge [this message]
2005-07-22 20:22 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2005-07-19 9:07 FX Coudert
2005-07-19 19:52 ` Christopher Faylor
2005-07-19 20:03 ` FX Coudert
2005-07-19 20:14 ` Christopher Faylor
2005-07-19 20:21 ` Daniel Jacobowitz
2005-07-21 2:10 ` Christopher Faylor
2005-07-21 2:14 ` Daniel Jacobowitz
2005-07-21 2:25 ` DJ Delorie
2005-07-21 2:40 ` Christopher Faylor
2005-07-21 2:58 ` DJ Delorie
2005-07-21 3:00 ` Daniel Jacobowitz
2005-07-21 3:27 ` DJ Delorie
2005-07-21 3:05 ` Christopher Faylor
2005-07-21 3:36 ` DJ Delorie
2005-07-21 3:27 ` Christopher Faylor
2005-07-25 13:38 ` François-Xavier Coudert
2005-07-25 15:22 ` Christopher Faylor
2005-07-25 20:49 ` DJ Delorie
2005-07-25 21:09 ` Christopher Faylor
2005-07-25 21:24 ` DJ Delorie
2005-07-25 21:33 ` Christopher Faylor
2005-07-25 22:06 ` Danny Smith
2005-09-15 0:47 ` Christopher Faylor
2005-07-26 7:38 ` Paolo Bonzini
2005-07-21 6:55 ` Paolo Bonzini
2005-07-21 2:58 ` Daniel Jacobowitz
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=20050722201547.DE1D3A8595@perpugilliam.csclub.uwaterloo.ca \
--to=rridge@csclub.uwaterloo.ca \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).