public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: "Stephan T. Lavavej" <stl@caltech.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: MinGW (Was: Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets)
Date: Mon, 19 May 2003 23:49:00 -0000	[thread overview]
Message-ID: <20030519164635.A8263@synopsys.com> (raw)
In-Reply-To: <000401c31e57$32c69910$3c9fd783@northwood>; from stl@caltech.edu on Mon, May 19, 2003 at 03:37:10PM -0700


> Given MinGW's importance as the only real way to run gcc on Windows, I don't
> see why it's not even a secondary platform for gcc.

Cygwin is of course an option (free for those not impacted by the GPL,
commercial license available for the rest).  However, the rules for
secondary platforms require a capable volunteer to sign up to be the
tester and coordinator for any needed bug fixes.  If a MinGW champion is
willing to take on that role, it will happen.  If not, it won't.

> I live in mortal fear that some day the MinGW developers will lose
> interest/be hit by a truck/whatever, and gcc will suddenly become unusable
> on Windows. Linux is great - I just put it on my second computer - but I
> think it's important to keep gcc functional on Windows, if for nothing else
> than to act as a gateway for new developers to get into the world of gcc.

OK.  What are you willing to do about it?

By that I mean that you, personally, could work to make things better if
you so desire.  You could be downloading CVS versions, running them,
reporting on problems, and asking for help with fixes.

Demanding that active GCC developers help isn't going to do anything;
their plates are already full.

  reply	other threads:[~2003-05-19 23:46 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 [this message]
2003-05-20  0:33 ` DJ Delorie
2003-05-21  3:27   ` Christopher Faylor
2003-05-20  4:22 ` Anthony Green
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=20030519164635.A8263@synopsys.com \
    --to=jbuck@synopsys.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).