Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!nosc!humu!pegasus!pilikia!art
From: art@pilikia.pegasus.com (Art Neilson)
Newsgroups: comp.unix.xenix
Subject: Re: XENIX 2.3.2 include files...
Message-ID: <1990Aug19.191859.26107@pilikia.pegasus.com>
Date: 19 Aug 90 19:18:59 GMT
References: <1990Aug18.091631.19939@dhw68k.cts.com>
Distribution: na
Organization: Pilikia, Honolulu
Lines: 25

In article <1990Aug18.091631.19939@dhw68k.cts.com> etg@dhw68k.cts.com (Eric Bennett) writes:
>
>I recently accquired the GCC C Compiler from another XENIX system and found
>out (when I un-tared it) that it did not come with the include files needed
>to run it. I realise that these files are system specific (i.e. you need the
>UNIX include files to run it on a UNIX system and the XENIX include........)
>but why do they have the compiler if you have to buy a C Development System
>in order to get the include files in order to use GCC? If you have purchased
>a C Compiler you obviously wouldn't need the GCC Compiler. But it appears,
>unless I am mistaken, that you can only get the include files from SCO when
>you purchase the Development System.
>
>It makes no sense to me.

It actually makes a lot of sense, the GCC compiler has a lot more features
and is a fully ANSI C compiler in contrast to the stock pcc that most of
us have.  It certainly isn't GNU's responsibility to provide system specific
header files, actually what the GNU guys are doing is developing an entire
OS free of AT&T licensing and the GNU C compiler happens to be one of the
tools they have completed for that environment to be.  I suppose an 
unscrupulous sort of person could just contact another XENIX site with the
SCO XENIX development system and get the header files from them, however.
-- 
Arthur W. Neilson III		| ARPA: art@pilikia.pegasus.com
Bank of Hawaii Tech Support	| UUCP: uunet!ucsd!nosc!pegasus!pilikia!art