public inbox for
 help / color / mirror / Atom feed
From: cyg Simple <>
Subject: Re: What is Cygwin and MinGW [WAS: Request new Ruby release]
Date: Tue, 15 May 2018 13:18:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I'm moving this to the Cygwin-Talk list.

On 5/14/2018 7:48 PM, Steven Penny wrote:
> On Mon, 14 May 2018 10:31:18, cyg Simple wrote:

>> And you a free to do so.  MinGW isn't GCC
> yes it is. when you compile GCC, as i have done:
> you choose a target. normally for this community that is
> "x86_64-pc-cygwin", but
> in my case it is "x86_64-w64-mingw32". but you dont use some magical
> "MinGW"
> repo, its the same GCC. granted, you do need to also install the target
> "binutils", "headers" and "runtime", but the same source is used to
> build GCC
> itself.

And given this you think Cygwin is also GCC.  WRONG, MinGW and Cygwin
are just the runtime libraries required to build GCC and other packages.
 GCC is a separate entity that has its own process of accepting patches
for using runtime libraries.  Binutils also is a separate entity that
uses even different methods of patching requirements as both Cygwin and
GCC.  Anyone who states that the GCC product is an entity other than GCC
isn't thinking clearly about the various pieces and parts.

Now to make Cygwin or MinGW useful you need the other pieces and parts
but those pieces and parts do not become the entity of Cygwin or MinGW.
Cygwin and MinGW remain a separate entity providing the runtime
libraries to use to build other pieces and parts.

cyg Simple

       reply	other threads:[~2018-05-15 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2018-05-15 13:18   ` cyg Simple [this message]
2018-05-15 14:02   ` Request new Ruby release cyg Simple

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).