From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 638 invoked by alias); 24 Feb 2009 12:37:42 -0000 Received: (qmail 628 invoked by uid 22791); 24 Feb 2009 12:37:41 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-fx0-f167.google.com (HELO mail-fx0-f167.google.com) (209.85.220.167) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Feb 2009 12:37:32 +0000 Received: by fxm11 with SMTP id 11so2905030fxm.2 for ; Tue, 24 Feb 2009 04:37:28 -0800 (PST) Received: by 10.103.105.1 with SMTP id h1mr4291021mum.13.1235479048125; Tue, 24 Feb 2009 04:37:28 -0800 (PST) Received: from ?82.6.108.62? (cpc2-cmbg8-0-0-cust61.cmbg.cable.ntl.com [82.6.108.62]) by mx.google.com with ESMTPS id a1sm18834108ugf.14.2009.02.24.04.37.27 (version=SSLv3 cipher=RC4-MD5); Tue, 24 Feb 2009 04:37:27 -0800 (PST) Message-ID: <49A3EC2B.5040607@gmail.com> Date: Tue, 24 Feb 2009 12:37:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: GCC4 status. References: <49A36143.50305@gmail.com> <49A37084.3090708@users.sourceforge.net> <49A37423.4050006@gmail.com> <49A38010.80906@cwilson.fastmail.fm> In-Reply-To: <49A38010.80906@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2009-02/txt/msg00131.txt.bz2 Charles Wilson wrote: > Dave Korn wrote: >> it's going to be a fairly non-standard >> x-compiler in that it won't go into the usual $prefix/$target sysroot, it's >> going to look for headers and libs directly where they live under the native >> prefix in /usr/include/mingw /usr/include/w32api /lib/mingw and /lib/w32api, >> and it's going to use the native 'as' and 'ld'. So it's going to be an ugly >> hybrid beast.... > > Why? Why shouldn't it just be a normal, vanilla, cross-compiler? Just > because we don't want two copies of w32api and mingw-runtime, or a > cross-ld/cross-as? Yep, these were my original reasons. > I think the maintenance headaches associated with an "ugly hybrid beast" > outweigh those other, tiny, costs... Well, I'm as allergic as cgf seems to be to the idea of having duplicated-and-potentially-inconsistent sets of the same files around the place, but as the downthread consensus seems to be settling on, we can rearrange things to have a proper $prefix/$target dir and build a proper one. (More to come in follow-on responses.) cheers, DaveK