Xref: utzoo comp.lang.c:32799 comp.unix.questions:26148
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!ucsd!ucbvax!unisoft!rembo
From: rembo@unisoft.UUCP (Tony Rems)
Newsgroups: comp.lang.c,comp.unix.questions
Subject: Re: C Compiler under Unix System VR4
Message-ID: <3159@unisoft.UUCP>
Date: 11 Oct 90 22:31:24 GMT
References: <125@alfrat.uucp> <3158@unisoft.UUCP>
Reply-To: rembo@unisoft.UUCP (Tony Rems)
Lines: 28

In article <3158@unisoft.UUCP> rembo@unisoft.UUCP (Tony Rems) writes:
>In article <125@alfrat.uucp> roy@alfrat.UUCP (Roy Phillips) writes:
>>The standard header files supplied with AT&T's UNIX System V Release 4.2
>>contains pre-processor commands such as the following:
>>
>>   #if #machine(pdp11)
>>
>>The C preprocessor supplied has no problems with this, but my preferred C
>>compiler, gcc, objects, even in it's '-ansi' mode.  So I guess it's
>>not ANSI C.  
>>
>>My questions are::
>>
>>1. Does anyone know about this pre-processor syntax? and is it
>>   supposed to be standard on SysVR4?
>>
>>2. Assuming yes to the above, is there a patch for 'gcc' to cater for it?
>>
>>As well as the above, the organisation of the library directory has changed
>>somewhat - 'gcc' can't find 'crt0.o', which is now in /usr/ccs/lib, instead
>>of /usr/lib (the same goes for most of the libraries).
>>

One more thing.  Although I haven't confirmed this, it seem that 
the #if #machine construct *is* ANSI, but that gcc is not 
entirely ANSI (even with the -ansi option).

-Tony