public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: rridge@csclub.uwaterloo.ca (Ross Ridge)
To: DJ Delorie <dj@redhat.com>
Cc: rridge@csclub.uwaterloo.ca, gcc@gcc.gnu.org
Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32
Date: Thu, 21 Jul 2005 17:32:00 -0000	[thread overview]
Message-ID: <20050721173214.8EF71A854B@perpugilliam.csclub.uwaterloo.ca> (raw)
In-Reply-To: <200507211619.j6LGJ5JT025154@greed.delorie.com>

Ross Ridge wrote:
> You already have a not-so-small C program that's supposed to know
> where as and ld are.

DJ Delorie wrote:
> You're forgetting about configure.

I don't see how the existance of configure changes the fact the GCC
compiler driver exists, is capable of running and as and ld, and is
supposed to know where they are.  It even does PATH-like searches.
Why not just fix it so it runs the correct version of as and ld directly
during the bootstrap process?  Add an a "--use-bootstrap-binutils" flag
or a "--with-ld=<file>" flag to the compiler driver, that way the newly
built compiler driver can directly execute the version of ld and as the
current makefile hack is trying to force it into running.

						Ross Ridge

-- 
 l/  //	  Ross Ridge -- The Great HTMU
[oo][oo]  rridge@csclub.uwaterloo.ca
-()-/()/  http://www.csclub.uwaterloo.ca/u/rridge/ 
 db  //	  

  reply	other threads:[~2005-07-21 17:32 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 [this message]
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
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=20050721173214.8EF71A854B@perpugilliam.csclub.uwaterloo.ca \
    --to=rridge@csclub.uwaterloo.ca \
    --cc=dj@redhat.com \
    --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).