From: DJ Delorie <dj@redhat.com>
To: me@cgf.cx
Cc: gcc@gcc.gnu.org, fxcoudert@gmail.com,
dannysmith@users.sourceforge.net, gcc-patches@gcc.gnu.org,
ian@airs.com
Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32
Date: Thu, 21 Jul 2005 02:25:00 -0000 [thread overview]
Message-ID: <200507210225.j6L2P6YI000508@greed.delorie.com> (raw)
In-Reply-To: <20050721021003.GA23290@trixie.casa.cgf.cx> (message from Christopher Faylor on Wed, 20 Jul 2005 22:10:03 -0400)
> Except that "cp" is already used as a fallback for when "ln" doesn't
> work. If the tool is likely not to work after a "cp" then shouldn't the
> fallback condition be to always create a shell script (or .bat file)?
One could argue that, in the case with ln/cp, we *know* we're dealing
with GNU tools which don't care where they are, but in the case with a
system (i.e. third party) tool, we don't know, hence the script.
There's also the complexity of locating a utility in $PATH, which may
even change between configure and make.
IMHO for MinGW, we (1) know that we're using GNU tools, and (2)
realize we have an exceptional situation wrt the build system. I
think this justifies an exception test in that snippet of code.
next prev parent reply other threads:[~2005-07-21 2:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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
2005-07-22 20:22 ` Mark Mitchell
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=200507210225.j6L2P6YI000508@greed.delorie.com \
--to=dj@redhat.com \
--cc=dannysmith@users.sourceforge.net \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=me@cgf.cx \
/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).