From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15408 invoked by alias); 11 Jun 2004 22:45:22 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 15400 invoked from network); 11 Jun 2004 22:45:20 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.5) by sourceware.org with SMTP; 11 Jun 2004 22:45:20 -0000 Received: (qmail 18488 invoked from network); 11 Jun 2004 22:45:20 -0000 Received: from taltos.codesourcery.com (zack@66.92.218.83) by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 11 Jun 2004 22:45:20 -0000 Received: by taltos.codesourcery.com (sSMTP sendmail emulation); Fri, 11 Jun 2004 15:45:19 -0700 To: "Aaron W. LaFramboise" Cc: mark@codesourcery.com, gcc-patches@gcc.gnu.org, dj@redhat.com Subject: Re: PATCH to support native Windows builds References: <200406112059.i5BKxnWv025590@sirius.codesourcery.com> <40CA3211.5030405@aaronwl.com> From: Zack Weinberg Date: Fri, 11 Jun 2004 23:56:00 -0000 In-Reply-To: <40CA3211.5030405@aaronwl.com> (Aaron W. LaFramboise's message of "Fri, 11 Jun 2004 17:28:33 -0500") Message-ID: <87r7sl7lz4.fsf@taltos.codesourcery.com> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-06/txt/msg00822.txt.bz2 "Aaron W. LaFramboise" writes: > Mark Mitchell wrote: >> This patch provides support for building GCC on native Windows (i.e., >> MinGW) as opposed to Cygwin. > > One concern I have is the Ctrl-C support. > > Presently Ctrl-C support is broken on all of GCC under > MinGW. Specifically, when you send a break from the console, it will > the toplevel gcc but not any invoked subprocesses. Does it make sense > to hack it into just collect2 when it doesn't work anywhere else? The code that's under debate here is not the Ctrl-C support in collect2. That stuff is the minimum necessary to get GCC to build in a cross-compile configuration with host=mingw; no one thinks it's ideal, but we don't know how to do it right. > While I am not aware of anyone working on improving Ctrl-C, perhaps I > personally might be interested in fixing this now that its come up. I'd be very glad if a competent Windows programmer would tackle this, but please consider it a separate issue from the pexecute changes. zw