From: Daniel Jacobowitz <drow@false.org>
To: gcc@gcc.gnu.org, FX Coudert <fxcoudert@gmail.com>,
dannysmith@users.sourceforge.net, patch <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:14:00 -0000 [thread overview]
Message-ID: <20050721021426.GA24051@nevyn.them.org> (raw)
In-Reply-To: <20050721021003.GA23290@trixie.casa.cgf.cx>
On Wed, Jul 20, 2005 at 10:10:03PM -0400, Christopher Faylor wrote:
> On Tue, Jul 19, 2005 at 04:21:04PM -0400, Daniel Jacobowitz wrote:
> >On Tue, Jul 19, 2005 at 04:14:04PM -0400, Christopher Faylor wrote:
> >>Ok. Given that 'cp' was an acceptable fallback in the original version
> >>of the above script, I wonder why 'cp' wasn't used instead of creating
> >>a shell script wrapper.
> >
> >Because it is desirable to leave the tools where they were:
>
> 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)?
That's basically what it does now; the only case which uses ln || cp is
for tools in the build directory, in which case they obviously are not
in their install location.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-21 2:14 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 [this message]
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
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=20050721021426.GA24051@nevyn.them.org \
--to=drow@false.org \
--cc=dannysmith@users.sourceforge.net \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.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).