public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bonzini" <bonzini@gnu.org>
To: <gcc@gcc.gnu.org>
Cc: <stl@caltech.edu>, <eric@umginc.net>
Subject: Re: MinGW (Was: Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets)
Date: Tue, 20 May 2003 17:52:00 -0000	[thread overview]
Message-ID: <000701c31ef6$c1d73340$59df1d97@bonz> (raw)

> When building other software packages in Cygwin, there is always the switch
> -mno-cygwin available to disable linking to Cygwin DLLs. *But*, you'll need to
> make sure that the package is not making any Unix-specific calls for it to
> work, which unfortunately, GCC has those fork / exec / kill calls.
>
> Eric

configure should properly detect these as absent when CC="gcc -mno-cygwin".  Moreover,
with -mno-cygwin you don't define __unix__ and __CYGWIN__, but __WIN32__ and
__MSVC_CRT__ (not sure about the spelling of this last one).  The problem is that bugs
in the MinGW port are often bound to show up with -mno-cygwin as well.

Paolo

             reply	other threads:[~2003-05-20 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 17:52 Bonzini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-20  1:24 MinGW (Was " Nathanael Nerode
2003-05-21  3:33 ` Christopher Faylor
2003-05-20  1:16 MinGW (Was: " Stephan T. Lavavej
2003-05-20  4:27 ` Ranjit Mathew
2003-05-20 16:15 ` E. Weddington
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

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='000701c31ef6$c1d73340$59df1d97@bonz' \
    --to=bonzini@gnu.org \
    --cc=eric@umginc.net \
    --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).