From: Anthony Green <green@redhat.com>
To: stl@caltech.edu
Cc: gcc@gcc.gnu.org
Subject: Re: MinGW (Was: Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets)
Date: Tue, 20 May 2003 04:22:00 -0000 [thread overview]
Message-ID: <1053401105.7114.165.camel@escape> (raw)
In-Reply-To: <000401c31e57$32c69910$3c9fd783@northwood>
On Mon, 2003-05-19 at 15:37, Stephan T. Lavavej wrote:
> I'm talking about MinGW, which - as far as I can tell - receives fairly
> little attention from the gcc developers and the community in general,
Well, I don't know about that. The gcj maintainers and other
contributors have put a lot of work into 3.3. I think we were just one
patch short of building out of the box...
http://www.thisiscool.com/gcc33_mingw.htm
Considering the level of interest and activity these past few months,
I'd be really surprised if 3.4 didn't build/work out of the box.
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
next prev parent reply other threads:[~2003-05-20 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 22:40 Stephan T. Lavavej
2003-05-19 23:49 ` Joe Buck
2003-05-20 0:33 ` DJ Delorie
2003-05-21 3:27 ` Christopher Faylor
2003-05-20 4:22 ` Anthony Green [this message]
2003-05-20 1:16 Stephan T. Lavavej
2003-05-20 4:27 ` Ranjit Mathew
2003-05-20 16:15 ` E. Weddington
2003-05-20 1:24 MinGW (Was " Nathanael Nerode
2003-05-21 3:33 ` Christopher Faylor
2003-05-20 17:52 MinGW (Was: " Bonzini
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=1053401105.7114.165.camel@escape \
--to=green@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=stl@caltech.edu \
/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).