From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Mailing List: CygWin-Apps <cygwin-apps@cygwin.com>
Subject: Re: GCC4 status.
Date: Tue, 24 Feb 2009 05:27:00 -0000 [thread overview]
Message-ID: <49A38553.2080801@cwilson.fastmail.fm> (raw)
In-Reply-To: <20090224051757.GA15043@ednor.casa.cgf.cx>
Christopher Faylor wrote:
> On Tue, Feb 24, 2009 at 12:05:20AM -0500, 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?
>>
>> I think the maintenance headaches associated with an "ugly hybrid beast"
>> outweigh those other, tiny, costs...
>
> I agree. I think we should relocate
relocate? But the regular cygwin gcc needs at least w32api, and that
location is hardcoded in its specs file. Which means that relocate
implies -> respin gcc-3.4.4-999, and respin gcc-4.2.3. And it doesn't
really make sense for the cygwin-gcc specs to specify "always look in
/usr/i686-pc-mingw32/include/[w32api]". Whuh, huh? *-mingw32?
It makes more sense to me that we have two different w32api packages:
the "regular" one that installs into /usr/[include|lib]/w32api, and a
mingw-cross-w32api that installs into
/usr/${mingw-triple}/[include|lib]/[w32api].
mingw-runtime...sure, that could probably be "relocated" without
trouble. I don't think the "regular" cygwin gcc should care about that.
> mingw and w32api into standard
> locations. That was part of the reason for getting rid of -mno-cygwin.
--
Chuck
next prev parent reply other threads:[~2009-02-24 5:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 2:44 Dave Korn
2009-02-24 3:04 ` Dave Korn
2009-02-24 3:59 ` Yaakov (Cygwin/X)
2009-02-24 4:05 ` Dave Korn
2009-02-24 5:05 ` Charles Wilson
2009-02-24 5:18 ` Christopher Faylor
2009-02-24 5:27 ` Charles Wilson [this message]
2009-02-24 5:51 ` Christopher Faylor
2009-02-24 6:40 ` Yaakov (Cygwin/X)
2009-02-24 9:15 ` Corinna Vinschen
2009-02-24 16:35 ` Christopher Faylor
2009-02-24 16:53 ` Corinna Vinschen
2009-02-24 18:13 ` Dave Korn
2009-02-25 14:21 ` Corinna Vinschen
2009-02-25 17:21 ` Dave Korn
2009-02-25 17:37 ` Corinna Vinschen
2009-02-26 4:36 ` Dave Korn
2009-02-26 5:05 ` Danny Smith
2009-02-26 3:37 ` Charles Wilson
2009-02-26 5:16 ` Danny Smith
2009-02-26 5:36 ` Charles Wilson
2009-02-26 5:58 ` Dave Korn
2009-02-26 3:29 ` Charles Wilson
2009-02-26 3:47 ` Yaakov (Cygwin/X)
2009-02-26 3:54 ` Charles Wilson
2009-02-26 4:23 ` Dave Korn
2009-02-24 12:37 ` Dave Korn
2009-02-24 14:29 ` Charles Wilson
2009-02-24 14:41 ` Dave Korn
2009-02-24 16:12 ` Christopher Faylor
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=49A38553.2080801@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin-apps@cygwin.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).