From: CRDGW2::CRDGW2::MRGATE::"SMTP::PREP.AI.MIT.EDU::HELP-GCC-REQUEST" 28-JAN-1991 08:46:48.56 To: MRGATE::"ARISIA::EVERHART" CC: Subj: gcc and SunOs 4.1 Received: by crdgw1.ge.com (5.57/GE 1.80) id AA14739; Mon, 28 Jan 91 08:35:38 EST Received: by life.ai.mit.edu (4.1/AI-4.10) id AA22315; Mon, 28 Jan 91 06:14:12 EST Return-Path: Received: from tut.cis.ohio-state.edu by life.ai.mit.edu (4.1/AI-4.10) id AA22290; Mon, 28 Jan 91 06:10:38 EST Received: by tut.cis.ohio-state.edu (5.61-kk/5.910105) id AA28895; Mon, 28 Jan 91 06:05:43 -0500 Received: from USENET by tut.cis.ohio-state.edu with netnews for help-gcc@prep.ai.mit.edu (help-gcc@prep.ai.mit.edu) (contact usenet@tut.cis.ohio-state.edu if you have questions) Date: 28 Jan 91 00:48:10 GMT From: mcsun!ukc!edcastle!aipna!rjc@uunet.uu.net (Richard Caley) Organization: Center for Speech Technology Research Subject: gcc and SunOs 4.1 Message-Id: Sender: help-gcc-request@prep.ai.mit.edu To: help-gcc@prep.ai.mit.edu Apologies if this is a FAQ. There seem to be major type clashes between gcc (specifically stddefs.h, but possibly also internaly) and the Sun supplied header files for SunOs 4.1 All of the errors seem to localise to the sun header sys/systypes.h which defines things like size_t in a way which clashes with stddefs.h. This makes life dificult when trying to compile anything even vaguely ANSIised. So, two questions: 1: Is there a relatively neat work-around which we can include in our system without making the people we deliver it to ill? 2: If we end up changine headers, which way is least likely to cause death and mayhem, changing gcc's headers to conform to suns or creating a gcc specific version of sun's header with the gcc definitions in it. particularly worrying, though not directly a problem for us, is the fact that gcc and SunOs have a totally different idea of how big a wide character is. -- rjc@cstr.ed.ac.uk Well, ok, so unsigned long vs long for size_t will _probably_ never cause problems, except in my aesthetics...