Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!van-bc!ubc-cs!nebulus!root
From: root@nebulus.UUCP (Dennis S. Breckenridge)
Newsgroups: comp.unix.questions
Subject: Re: ANSI header files
Message-ID: <1990Mar29.145856.14614@nebulus.UUCP>
Date: 29 Mar 90 14:58:56 GMT
References: <2105@kiwi.mpr.ca> <12431@smoke.BRL.MIL> <1990Mar28.144531.12008@druid.uucp>
Reply-To: root@nebulus.UUCP (Dennis S. Breckenridge)
Organization: Alchemy Mindworks, Vancouver, Canada
Lines: 21

In article <1990Mar28.144531.12008@druid.uucp> darcy@druid.UUCP (D'Arcy J.M. Cain) writes:
> sort of OK but they don't have prototypes.  I have been slowly upgrading
                                              --------> WOW <----------
> the header files to be more ANSI compliant so that they work with gcc
> better.

Darcy, if you arbitrarily stomp on /usr/include with the ANSI C or gcc
header files you probably will get to a point where your kernel will 
not compile and link. There are *MANY* dependencies on the various 
XENIXisms found all over the place. TIOCGWINSZ is the one that frags
me all the time. If you use some of the net programs like "rn" that
take best guess at thier environment they find all kinds of axymorons
and try to build a XENIX - SYSV version of rn. I would put the gcc
headers in ~include/gcc and then add -I/usr/include/gcc to the compile
line. 

-- 
-----------------------------------------------------------------------------
Dennis S. Breckenridge  (604) 277-7413   dennis@nebulus.uucp           VE7TCP
               EMACS: Eight Megabytes And Constantly Swapping!
-----------------------------------------------------------------------------