home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!usc!sdd.hp.com!mips!darwin.sura.net!jhunix.hcf.jhu.edu!andy
- From: andy@jhunix.hcf.jhu.edu (Andy Poling)
- Subject: Re: Problem with C compiler/pre-compiler in ANSI mode
- Message-ID: <1992Aug17.004331.100@jhunix.hcf.jhu.edu>
- Followup-To: poster
- Summary: was me...
- Keywords: cc, cpp, acpp
- Organization: HAC - Johns Hopkins University, Baltimore
- References: <1992Aug15.232605.23822@jhunix.hcf.jhu.edu>
- Date: Mon, 17 Aug 1992 00:43:31 GMT
- Lines: 27
-
- In article <1992Aug15.232605.23822@jhunix.hcf.jhu.edu> andy@jhunix.hcf.jhu.edu (Andy Poling) writes:
- >
- >I'm encountering what seems to be a problem with the Development Option 4.0
- >C compiler and/or pre-compiler.
- >
- >When I invoke cc with the "-ansi" option (so that it won't shout at me about
- >void pointer usage in prototypes in the SGI-provided header files) it stops
- >processing some header files properly - e.g. /usr/include/sys/signal.h . It
- >seems ignorant of the macro sigmask() which is defined in
- >/usr/include/sys/signal.h and it seems to have ignored the BSD prototypes in
- >/usr/include/sys/signal.h and seems to be using the SysV prototypes.
-
- Several people were kind enough to point out to me that Posix and/or BSD
- signal functions are only prototyped if __EXTENSIONS__ or __POSIX_SOURCE are
- defined (and they are in "-xansi", or default, mode).
-
- I can no longer reproduce the complaints about void pointers, so I am
- asuming that I was doing something something strange (and/or wrong).
-
- Thanks to the people who responded.
-
- -Andy
-
- Andy Poling Internet: andy@jhunix.hcf.jhu.edu
- UNIX Systems Programmer Bitnet: ANDY@JHUNIX
- Homewood Academic Computing Voice: (410)516-8096
- Johns Hopkins University UUCP: uunet!mimsy!aplcen!jhunix!andy
-