Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Wed, 24 Sep 2003 18:32:52 -0400 (EDT)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	"Hannu E K Nevalainen (garbage mail)" <garbage_collector AT telia DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	RE: __cygwin__ ++ (RE: getuid() and root)
In-Reply-To:	<NGBBLLIAMFLGJEOAJCCEGEIIDEAA.garbage_collector@telia.com>
Message-ID:	<Pine.GSO.4.56.0309241829300.3193@slinky.cs.nyu.edu>
References:	<NGBBLLIAMFLGJEOAJCCEGEIIDEAA DOT garbage_collector AT telia DOT com>
Importance:	Normal
MIME-Version:	1.0

On Thu, 25 Sep 2003, Hannu E K Nevalainen (garbage mail) wrote:

> > From: Christopher Faylor
>
> > On Wed, Sep 24, 2003 at 09:21:38PM +0200, Hannu E K Nevalainen
> > (garbage mail) wrote:
>
> > >I've been thinking that there is a need for a __NOCYGWIN__
> > define too (to
> > >be set when -mno-cygwin is used).
> > >Any thoughts about this? Good(tm) or Bad(tm)?
> >
> > Bad.
> >
> > Rather than cast around in the dark here,
>
> Yes I'm in the dark, thank you I *DO* know that.
>  _THAT IS WHY I'M HERE_ - I've said things inline with that before. You WILL
> most likely read words in style with that - from me - many times over still.

Hannu,

This was not an offensive comment, but a figure of speech.

> >you should be investigating gcc
> > options that tell you what is available.
>
>  I've done that, as you can see below. BUT, as I do "cast around in the
> dark" I haven't got ALL the answers; i.e:
>
> >  I just did this and came up
> > with this incantation:
> >
> >       gcc -dM -E -xc /dev/null
> >
> > There's probably an easier way to do this (and if there is, there will
> > be five responses to this message pointing it out) but try the above
> > command.  Then try:
> >
> >       gcc -mno-cygwin -dM -E -xc /dev/null
> >
> > and compare/contrast the results.
>
> +#define __MINGW32__ 1
>
>  Thanks, that's a good one. I bet I'll be using that one shortly.
>
>  NOW - to remove the "darkness";
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This has to be *documented* too. That obviously hasn't happened yet.
>
> /Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
> -- UTC+01, DST -> UTC+02  --
> [snip]

Why are you looking for a MinGW-specific #define in Cygwin documentation?
Granted, it doesn't seem to be in MinGW docs either, but isn't that where
you should have looked for it?

FWIW, Google turns up <http://google.com/search?q=mingw+gcc+defined>
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -