public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jesper Eskilson <jojo@virtutech.se>
To: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Cc: cygwin@cygwin.com
Subject: Re: Up-to-date info on '-mno-cygwin' vs. Mingw32
Date: Thu, 30 Aug 2001 23:52:00 -0000	[thread overview]
Message-ID: <u67pu9cwwmn.fsf@rachel.vtab.com> (raw)
In-Reply-To: <4.3.1.2.20010830093245.02235f08@pop.ma.ultranet.com>

"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> writes:

> The difference is in the build environment, not the result.  

According to the FAQ, support for the -mno-cygwin flag "has been weak
and flaky, [...] and maintenance of the option has *not* been a
priority in development", and the FAQ recommends that one uses a
separate MingW compiler set. Is this accurate?

/Jesper
-- 
-------------------------------------------------------------------------
Jesper Eskilson                                         jojo@virtutech.se
Virtutech                                         http://www.virtutech.se
-------------------------------------------------------------------------

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2001-08-30 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30  4:25 Jesper Eskilson
2001-08-30  6:33 ` Larry Hall (RFK Partners, Inc)
2001-08-30  8:27   ` Gerald W. Shapiro
2001-08-30 23:52   ` Jesper Eskilson [this message]
2001-08-31  4:29     ` David Carter
2001-08-31  7:36       ` Jesper Eskilson
2001-08-31  7:53       ` Christopher Faylor
2001-08-31 14:53       ` James Youngman
2001-09-01 19:08     ` Paul G.
2001-09-08  8:01       ` David Starks-Browning
2001-08-30 17:32 ` Paul G.

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=u67pu9cwwmn.fsf@rachel.vtab.com \
    --to=jojo@virtutech.se \
    --cc=cygwin@cygwin.com \
    --cc=lhall@rfk.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).