From: michael AT weiser DOT saale-net DOT de (Michael Weiser) Subject: Re: I: gcc ... -U_WIN32 ... may cause problems 28 Aug 1998 22:39:18 -0700 Message-ID: <199808281822.UAA00348.cygnus.gnu-win32@weiser.saale-net.de> References: <01BDD20D DOT B63709B0 DOT MCzapski AT openplus DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "MCzapski AT openplus DOT com DOT au" Cc: gnu-win32 AT cygnus DOT com Hello Michael, you wrote: >Cygwin32 but unix-specific daemon code is compiled instead, for example. To >avoid coding #if defined construct as shown I decided to undefine _WIN32 when >compiling in Cygwin32 environment by using a command line of a form "gcc ... >-U_WIN32 ...". Before I did that the application worked fine however as soon Wouldn't it be cleaner and easier to code something like #if defined __unix__ || defined __CYGWIN32__ .... #endif and #if defined _WIN32 && !defined __CYGWIN32__ .... #endif around parts of your program that should behave like on unix under cygwin? IMHO that wouldn't be more effort than solving your current problem and all the others that will arise if something in the headers or the cygwin tools gets changed. -- tschoe, Micha - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".