Article View: gnu.gcc.help
Article #958Re: gcc 2.3.2 on SCO 3.2.4 (__STDC__)
From: Giles Lean
Date: Wed, 20 Jan 1993 21:29
Date: Wed, 20 Jan 1993 21:29
34 lines
1653 bytes
1653 bytes
wes@dd.dk (Mads Westermann) writes: >Sometime ago there was a discussion on a problem involving the >definition of __STDC__ in gcc versus cc on SCO 3.2.4. I have now >run into the problem and cannot remember what the solution was !! I try compiling with -D__STDC__=0 -D_POSIX_SOURCE and work from there. The reason for -D__STDC__=0 is that there are quite a few places where a construct such as #if defined(_POSIX_SOURCE) || defined(_XOPEN_SOURCE) || !__STDC__ ... posix and x-open but *not* ANSI code ... #endif or #if !__STDC__ ... unix non ANSI code ... #endif is used. The cc manual page indicates what symbols the SCO pre-processor defines, but not their values. I don't like __STDC__=0 and would prefer something like _UNIX_SOURCE. Giles P.S. I deleted comp.unix.sysv386 as that group has been replaced by comp.unix.pc-clone.32bit. -- Giles Lean at Pro Medicus <giles@promed.com.au>
Technical Details
Message-ID:
<1993Jan20.212953.14746@promed.com.au>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!yarrina.connect.com.au!medicus.promed.com.au!gilesReferences:
<1993Jan20.123122.12886@dd.dk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,93d4a3c9cf7a58e3,start X-Google-Attributes: gid11318c,public X-Google-Thread: 1122ea,93d4a3c9cf7a58e3,start X-Google-Attributes: gid1122ea,public X-Google-ArrivalTime: 1993-01-20 13:47:46 PST Newsgroups: gnu.gcc.help,biz.sco.general Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!yarrina.connect.com.au!medicus.promed.com.au!giles From: giles@promed.com.au (Giles Lean) Subject: Re: gcc 2.3.2 on SCO 3.2.4 (__STDC__) Organization: Pro Medicus, Melbourne, Australia Date: Wed, 20 Jan 93 21:29:53 GMT Message-ID: <1993Jan20.212953.14746@promed.com.au> References: <1993Jan20.123122.12886@dd.dk> Keywords: sco 3.2.4 gcc 2.3.2 __STDC__ ansi c Lines: 34