public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: gcc@gcc.gnu.org, dannysmith@users.sourceforge.net
Subject: Re: PING [4.1 regression, patch] build i686-pc-mingw32
Date: Thu, 15 Sep 2005 00:47:00 -0000	[thread overview]
Message-ID: <20050915004740.GD31774@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20050725213319.GC14068@trixie.casa.cgf.cx>

On Mon, Jul 25, 2005 at 05:33:19PM -0400, Christopher Faylor wrote:
>On Mon, Jul 25, 2005 at 05:23:54PM -0400, DJ Delorie wrote:
>>>Maybe one solution would be to patch pex-win32 for mingw so that it
>>>could understand '#!' style shell scripts?  That would at least allow
>>>bootstrapping.
>>
>>That would be wonderful, and that's exactly the right place to put it
>>too.  I'm assuming I can persuade one of you to do that?  ;-)
>>
>>I'm going to define pex-win32.c as being within the realm of the mingw
>>maintainership (if you hadn't assumed that already).
>
>I'd be happy to implement this.  I'd like to get Danny's opinion on this
>first, though, in case I missed something.

With DJ's (private) approval, I've checked in a fix to implement this.
Sorry for the long delay.

cgf

  parent reply	other threads:[~2005-09-15  0:47 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
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 [this message]
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=20050915004740.GD31774@trixie.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=dannysmith@users.sourceforge.net \
    --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).