getuid() and root

getuid() and root

[Kevin Van Workum]

I'm trying to compile SOpenPBS on Cygwin. SOpenPBS is the Scalable Open
Portable Batch System (www.supercluster.org). And I need some advice.

I have it compiled and running, with some ugly hacks. First, the daemons
want to run as user root. I can change this in the source to my login, but
I'd like to eventually make it available to others, so this is not a good
solution.  I'd like it to work similar to sshd or cron and have it run
using cygrunsrv, but I don't know how to do that. Any advice? Anyone
interested in using SPBS on Cygwin and/or helping me to port it?

Kevin Van Workum, PhD
National Institute of Standards and Technology
Polymers Division 224/B228

--
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/

Re: getuid() and root

[Corinna Vinschen]

On Tue, Sep 23, 2003 at 09:44:22AM -0400, Kevin Van Workum wrote:
> I'm trying to compile SOpenPBS on Cygwin. SOpenPBS is the Scalable Open
> Portable Batch System (www.supercluster.org). And I need some advice.
> 
> I have it compiled and running, with some ugly hacks. First, the daemons
> want to run as user root. I can change this in the source to my login, but
> I'd like to eventually make it available to others, so this is not a good
> solution.  I'd like it to work similar to sshd or cron and have it run
> using cygrunsrv, but I don't know how to do that. Any advice? Anyone
> interested in using SPBS on Cygwin and/or helping me to port it?

Remove (or better ifdef out) all checks for the root user account.
sshd is using the same approach.  We don't have a root user
concept so far so these test are a bit displaced on Cygwin.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

__CYGWIN__ ++ (RE: getuid() and root)

[Hannu E K Nevalainen (garbage mail)]

> From: Corinna Vinschen

<SNIP>
> Remove (or better ifdef out) all checks for the root user account.
> sshd is using the same approach.  We don't have a root user
> concept so far so these test are a bit displaced on Cygwin.

Sorry to butt in again... :-P

This is just to make things clear up a bit for myself...
Current status as I've understood it is; As -mno-cygwin _ISN'T_ used
 __CYGWIN__ and __CYGWIN32__ both will be #define 'd.

Now the big Q: What is the difference between those?
(Is it an 1.3.x vs 1.5.x issue?)

I'm rigth now testing the bladeenc mp3 encoder under cygwin.
It seems to be working well after my efforts. But I've had to ifdef in/out
some sections of code.
To eventually be able to hand out "nice" diffs, I need to be clear over any
differences here.

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --
--END OF MESSAGE--


--
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/

Re: __CYGWIN__ ++ (RE: getuid() and root)

[Corinna Vinschen]

On Tue, Sep 23, 2003 at 08:41:59PM +0200, Hannu E K Nevalainen (garbage mail) wrote:
> Current status as I've understood it is; As -mno-cygwin _ISN'T_ used
>  __CYGWIN__ and __CYGWIN32__ both will be #define 'd.
> 
> Now the big Q: What is the difference between those?

__CYGWIN__ is the correct one.  __CYGWIN32__ was the predecessor
(pre french revolution).  Kept for backward compatibility.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

RE: __CYGWIN__ ++ (RE: getuid() and root)

[Hannu E K Nevalainen (garbage mail)]

> From: Corinna Vinschen

> On Tue, Sep 23, 2003 at 08:41:59PM +0200, Hannu E K Nevalainen
> (garbage mail) wrote:
> > Current status as I've understood it is; As -mno-cygwin _ISN'T_ used
> >  __CYGWIN__ and __CYGWIN32__ both will be #define 'd.
> >
> > Now the big Q: What is the difference between those?
>
> __CYGWIN__ is the correct one.  __CYGWIN32__ was the predecessor
> (pre french revolution).  Kept for backward compatibility.
>
> Corinna

Thanks. The use of __CYGWIN__ is clear and sound.
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)?

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --


Searching the archives, w google (I'm VERY negative vs "htdig" right now)
	+"CYGWIN" +"-mno-cygwin" site:cygwin.com inurl:ml
gives 1450 hits...

I'm out of ideas on how to refine this - to find anything that matches
__NOCYGWIN__ or similar.

At times I'm VERY frustrated with search engines (e.g. google) for their
incapability to do what the help files indicate. Adding a "+" before a word,
as I have done above, is meant to REQUIRE that word to be in the items
shown. IMO this DOESN'T happen.

--END OF MESSAGE--


--
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/

Google (Was: Re: __CYGWIN__ ++ (RE: getuid() and root))

[Rolf Campbell]

Hannu E K Nevalainen (garbage mail) wrote:
> Searching the archives, w google (I'm VERY negative vs "htdig" right now)
> 	+"CYGWIN" +"-mno-cygwin" site:cygwin.com inurl:ml
> gives 1450 hits...
> 
> I'm out of ideas on how to refine this - to find anything that matches
> __NOCYGWIN__ or similar.
> 
> At times I'm VERY frustrated with search engines (e.g. google) for their
> incapability to do what the help files indicate. Adding a "+" before a word,
> as I have done above, is meant to REQUIRE that word to be in the items
> shown. IMO this DOESN'T happen.
It does, but google doesn't handle '-'s very well.  I thinks of it as a 
word seperator.



--
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/

Re: __cygwin__ ++ (RE: getuid() and root)

[Christopher Faylor]

On Wed, Sep 24, 2003 at 09:21:38PM +0200, Hannu E K Nevalainen (garbage mail) wrote:
>> From: Corinna Vinschen
>
>> On Tue, Sep 23, 2003 at 08:41:59PM +0200, Hannu E K Nevalainen
>> (garbage mail) wrote:
>> > Current status as I've understood it is; As -mno-cygwin _ISN'T_ used
>> >  __CYGWIN__ and __CYGWIN32__ both will be #define 'd.
>> >
>> > Now the big Q: What is the difference between those?
>>
>> __CYGWIN__ is the correct one.  __CYGWIN32__ was the predecessor
>> (pre french revolution).  Kept for backward compatibility.
>>
>> Corinna
>
>Thanks. The use of __CYGWIN__ is clear and sound.
>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, you should be investigating gcc
options that tell you what is available.  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.

--
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/

RE: __cygwin__ ++ (RE: getuid() and root)

[Hannu E K Nevalainen (garbage mail)]

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

>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  --



I looked before I wrote the thing above. I've looked AGAIN, NOW, this time
knowing WHAT to look for.
 "__CYGWIN__" is mentioned as "preprocessor symbol" - but "__MINGW32__"
isn't.

IMNSHO; Undocumented features could just as well be unimplemented.

Once again it has been prooved that _documentation_ may be the hardest part
of all. Sad but try: It is many times _forgotten_ altogether.

 Now Chris, YOU were complaining about me writing messages that generate
"five more" replies...
Imagine how many unwanted messages that undocumented feature will give you?

 THIS and the PREVIOUS one was just two. They could have been surpassed by
including __MINGW32__ in at least one of the docs.


$ pwd
/usr/share/doc/cygwin-doc-1.3

$ find -type f | xargs grep __CYGWIN__
./cygwin-ug-net-nochunks.html:#ifdef __CYGWIN__
./cygwin-ug-net-nochunks.html:#ifdef __CYGWIN__
./html/cygwin-ug-net/ntsec.html:#ifdef __CYGWIN__
./html/cygwin-ug-net/ntsec.html:#ifdef __CYGWIN__
./html/faq_4.html:We use _WIN32 to signify access to the Win32 API and
__CYGWIN__ for
./html/readme.html:__CYGWIN32__ to __CYGWIN__.  We will remove the old names
in a future
./txt/faq.txt:   We use _WIN32 to signify access to the Win32 API and
__CYGWIN__ for
./txt/readme.txt:__CYGWIN32__ to __CYGWIN__.  We will remove the old names
in a future

$ find -type f | xargs grep __MINGW32__

$ gcc -dumpspecs | grep MINGW32
%(cpp_cpu) %{posix:-D_POSIX_SOURCE}   %{mno-win32:%{mno-cygwin: %emno-cygwin
and mno-win32 are not compatible}}   %{mno-cygwin:-D__MSVCRT__ -D__MINGW32__
%{!ansi:%{mthreads:-D_MT}}}  %{!mno-cygwin:-D__CYGWIN32__ -D__CYGWIN__
%{!ansi:-Dunix} -D__unix__ -D__unix }
 %{mwin32|mno-cygwin:-DWIN32 -D_WIN32 -D__WIN32 -D__WIN32__
%{!ansi:-DWINNT}}  %{!nostdinc:%{!mno-win32|mno-cygwin:-idirafter
../include/w32api%s -idirafter ../../include/w32api%s}}

--

$ gcc -dM -E -xc /dev/null >gcc_cygwin
$ gcc -mno-cygwin -dM -E -xc /dev/null >gcc_nocygwin
$ diff -up gcc_cygwin gcc_nocygwin
--- gcc_cygwin        2003-09-24 23:28:38.000000000 +0200
+++ gcc_nocygwin      2003-09-24 23:29:06.000000000 +0200
@@ -1,12 +1,11 @@
 #define __DBL_MIN_EXP__ (-1021)
 #define __FLT_MIN__ 1.17549435e-38F
+#define _WIN32 1
 #define _X86_ 1
 #define __CHAR_BIT__ 8
 #define __WCHAR_MAX__ 65535U
 #define __DBL_DENORM_MIN__ 4.9406564584124654e-324
 #define __FLT_EVAL_METHOD__ 2
-#define __unix__ 1
-#define unix 1
 #define __i386__ 1
 #define __SIZE_TYPE__ unsigned int
 #define __DBL_MIN_10_EXP__ (-307)
@@ -17,23 +16,25 @@
 #define _stdcall __attribute__((__stdcall__))
 #define __SHRT_MAX__ 32767
 #define __LDBL_MAX__ 1.18973149535723176502e+4932L
-#define __CYGWIN__ 1
-#define __unix 1
+#define __MSVCRT__ 1
 #define __LDBL_MAX_EXP__ 16384
 #define __LONG_MAX__ 2147483647L
 #define __SCHAR_MAX__ 127
 #define __DBL_DIG__ 15
 #define __USER_LABEL_PREFIX__ _
 #define __STDC_HOSTED__ 1
+#define __WIN32 1
 #define __stdcall __attribute__((__stdcall__))
 #define __LDBL_MANT_DIG__ 64
 #define __FLT_EPSILON__ 1.19209290e-7F
 #define __tune_i686__ 1
 #define __LDBL_MIN__ 3.36210314311209350626e-4932L
 #define __WCHAR_TYPE__ short unsigned int
+#define __MINGW32__ 1
 #define __FLT_DIG__ 6
 #define __FLT_MAX_10_EXP__ 38
 #define __INT_MAX__ 2147483647
+#define WIN32 1
 #define __FLT_MAX_EXP__ 128
 #define __DECIMAL_DIG__ 21
 #define __DBL_MANT_DIG__ 53
@@ -47,9 +48,10 @@
 #define __tune_pentiumpro__ 1
 #define __fastcall __attribute__((__fastcall__))
 #define _fastcall __attribute__((__fastcall__))
-#define __CYGWIN32__ 1
 #define __USING_SJLJ_EXCEPTIONS__ 1
 #define __DBL_MAX_EXP__ 1024
+#define __WIN32__ 1
+#define WINNT 1
 #define __FLT_DENORM_MIN__ 1.40129846e-45F
 #define __LONG_LONG_MAX__ 9223372036854775807LL
 #define __FLT_MAX__ 3.40282347e+38F

--END OF MESSAGE--


--
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/

RE: __cygwin__ ++ (RE: getuid() and root)

[Igor Pechtchanski]

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@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/

RE: __cygwin__ ++ (RE: getuid() and root)

[Hannu E K Nevalainen (garbage mail)]

> From: Igor Pechtchanski

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

Then - I cannot do anything better than:

 *** Christopher: I am truly sorry. ***

With all this in mind, it looks like my knowledge of "sayings" is null and
void. It makes me even more sad. It opens up questions about my knowledge of
the English language - once again. :-[
Fine tuning needed, at least.

/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

 This is somewhat questionable IMO. No doubt that __MINGW32__ is something
that comes from the mingw project.
 But as it is available from the cygwin/bash command line it should be at
least MENTIONED in the cygwin docs too. Even a *broken* link could have
helped.

 As I was looking I had _no idea_ of WHAT to look for. This might have been
shortsighted of me, as you look on it now (with mingw in mind), but that is
how it was - I have no excuses WRT this.

--END OF MESSAGE--


--
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/

RE: __CYGWIN__ ++ FAQ change? ( faq.txt DIFF )

[Hannu E K Nevalainen (garbage mail)]

This is a quickly scribbled update of the FAQ. Contents is bare essentials
as I see it. Please do relevant "PTC"-actions.

$ diff -up /usr/share/doc/cygwin-doc-1.3/txt/faq.txt \
/usr/share/doc/cygwin-doc-1.3/txt/faq.txt.new
--- /usr/share/doc/cygwin-doc-1.3/txt/faq.txt   2003-09-04
19:46:02.000000000 +0200
+++ /usr/share/doc/cygwin-doc-1.3/txt/faq.txt.new       2003-09-25
20:48:42.000000000 +0200
@@ -3401,6 +3401,17 @@ Unix emulation environment and defining
 which think that they have to make special concessions for a Windows
 environment which Cygwin handles automatically.

+Note that using -mno-cygwin replaces __CYGWIN__ with __MINGW32__ as to
+tell which compiler (or settings) you're running.
+Check this out in detail by running e.g.
+       $ gcc <option> -dM -E -xc /dev/null >gcc_<option>
+with each <option> and then use the diff utility to check what the
+difference is in the output.
+Relevant <option> keywords;
+ --mno-cygwin
+ --mwin32
+ nothing (i.e. remove <option> ).
+
 How should I port my Unix GUI to Windows?
 -----------------------------------------

-- end of diff, NOTE EMPTY LINE! --

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- UTC+01, DST -> UTC+02  --
--END OF MESSAGE--


--
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/

RE: __CYGWIN__ ++ FAQ change? ( faq.txt DIFF )

[Igor Pechtchanski]

Hannu,

faq.txt is generated.  See
<http://cygwin.com/ml/cygwin/2003-09/msg01613.html> for the location of
the "real" faq.
	Igor

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

> This is a quickly scribbled update of the FAQ. Contents is bare essentials
> as I see it. Please do relevant "PTC"-actions.
>
> $ diff -up /usr/share/doc/cygwin-doc-1.3/txt/faq.txt \
> /usr/share/doc/cygwin-doc-1.3/txt/faq.txt.new
> --- /usr/share/doc/cygwin-doc-1.3/txt/faq.txt   2003-09-04
> 19:46:02.000000000 +0200
> +++ /usr/share/doc/cygwin-doc-1.3/txt/faq.txt.new       2003-09-25
> 20:48:42.000000000 +0200
> @@ -3401,6 +3401,17 @@ Unix emulation environment and defining
>  which think that they have to make special concessions for a Windows
>  environment which Cygwin handles automatically.
>
> +Note that using -mno-cygwin replaces __CYGWIN__ with __MINGW32__ as to
> +tell which compiler (or settings) you're running.
> +Check this out in detail by running e.g.
> +       $ gcc <option> -dM -E -xc /dev/null >gcc_<option>
> +with each <option> and then use the diff utility to check what the
> +difference is in the output.
> +Relevant <option> keywords;
> + --mno-cygwin
> + --mwin32
> + nothing (i.e. remove <option> ).
> +
>  How should I port my Unix GUI to Windows?
>  -----------------------------------------
>
> -- end of diff, NOTE EMPTY LINE! --
>
> /Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
> -- UTC+01, DST -> UTC+02  --
> --END OF MESSAGE--

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/

RE: __CYGWIN__ ++ FAQ change?

[Hannu E K Nevalainen]

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

> From: Igor Pechtchanski
> Sent: Thursday, September 25, 2003 10:03 PM

> Hannu,
> 
> faq.txt is generated.  See
> <http://cygwin.com/ml/cygwin/2003-09/msg01613.html> for the location of
> the "real" faq.
> 	Igor

 ...retry.

-- Changelog --
2003-10-16  Hannu E K Nevalainen  <garbage_collector@telia.com>

* how-programming.texinfo: Add some words about -mno-cygwin,
the difference with regard to preprocessor symbols and how to
investigate it further.
--

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- (DST) ? UTC+02 : UTC+01 --
--END OF MESSAGE--

[-- Attachment #2: how-programming.texinfo.diff --]
[-- Type: application/octet-stream, Size: 1346 bytes --]

--- /src/winsup/doc/how-programming.texinfo	2003-02-13 15:20:32.000000000 +0100
+++ /src/winsup/doc/how-programming.texinfo-Hannu	2003-10-16 20:22:24.000000000 +0200
@@ -558,7 +558,7 @@ If your scripts are in the current direc
 you would need to add /bin/sh in front of each and every shell script
 invoked in your Makefiles.
 
-@subsection What preprocessor do I need to know about?
+@subsection What preprocessor symbols do I need to know about?
 
 We use _WIN32 to signify access to the Win32 API and __CYGWIN__ for
 access to the Cygwin environment provided by the dll.
@@ -574,6 +574,17 @@ Unix emulation environment and defining 
 which think that they have to make special concessions for a Windows
 environment which Cygwin handles automatically.
 
+Note that using -mno-cygwin replaces __CYGWIN__ with __MINGW32__ as to
+tell which compiler (or settings) you're running.
+Check this out in detail by running e.g.
+       $ gcc <option> -dM -E -xc /dev/null >gcc_<option>.txt
+with each <option>. Then use the diff and grep utilities to check
+what the difference is.
+Relevant <option> keywords;
+ -mno-cygwin
+ -mwin32
+ nothing (i.e. remove <option> and use the default WRT this).
+
 @subsection How should I port my Unix GUI to Windows?
 
 There are two basic strategies for porting Unix GUIs to Windows.

[-- Attachment #3: Changelog --]
[-- Type: application/octet-stream, Size: 219 bytes --]

2003-10-16  Hannu E K Nevalainen  <garbage_collector@telia.com>

* how-programming.texinfo: Add some words about -mno-cygwin,
the difference with regard to preprocessor symbols and how to
investigate it further.


[-- Attachment #4: Type: text/plain, Size: 218 bytes --]

--
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/