Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!turnkey!jackv
From: jackv@turnkey.TCC.COM (Jack F. Vogel)
Newsgroups: comp.unix.i386
Subject: Re: compile errors with /usr/include/sys/types.h
Message-ID: <6730@turnkey.TCC.COM>
Date: 5 Mar 90 17:10:57 GMT
References: <1990Mar1.022620.23226@ice9.uucp>
Reply-To: jackv@turnkey.TCC.COM
Distribution: na
Organization: Turnkey Computer Consultants, Westchester, CA
Lines: 23

In article <1990Mar1.022620.23226@ice9.uucp> bgh@ice9.uucp (barry hannigan) writes:
>the following lines are excerpted from /usr/include/sys/types.h in ISC 2.0.2
 
>typedef	struct { int r[1]; }	*	physadr;
>typedef	char	*		caddr_t;  /* ?<core address> type */
>typedef	char *		faddr_t;  /* same as caddr_t for 8086/386 */
>they cause syntax errors when used.
 
Barry,	there is nothing wrong with types.h, what is actually happening is
that it is being included twice and the second pass through this stuff by
the preprocessor causes the syntax error. You need to search through the
include files, find the second inclusion and remove it. I have found the
X source to be notorious for this problem. Oh, BTW, the GNU gcc compiler
gives error messages that make it a lot more obvious what the problem is
(it actually tells you there was a previous declaration).

Disclaimer: I speak for myself, not for LCC.


-- 
Jack F. Vogel			jackv@seas.ucla.edu
AIX Technical Support	              - or -
Locus Computing Corp.		jackv@ifs.umich.edu