Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!mcsun!ukc!strath-cs!cs.glasgow.ac.uk!memex!scott
From: scott@memex.co.uk (Scott Williamson)
Newsgroups: comp.lang.c
Subject: Re: where to find all those #ifdef's and #defines
Message-ID: <343@memex.co.uk>
Date: 11 Jan 90 10:08:14 GMT
References: <40059@ames.arc.nasa.gov> <1990Jan9.174739.8828@iwarp.intel.com>
Reply-To: scott@memex.co.uk (Scott Williamson)
Organization: Memex Ltd., East Kilbride, Scotland
Lines: 24

In article <1990Jan9.174739.8828@iwarp.intel.com> merlyn@iwarp.intel.com (Randal Schwartz) writes:
>In article <40059@ames.arc.nasa.gov>, dwhitney@pioneer (David Whitney- RCD) writes:
>| 
>| Does anyone know who, what, or where to find these definitions for each
>| machine?  What I'd like (ideally) is a list of the variables that
>| are #define'ed at any one time.  Thanks,
>
>Here it is (and it's not even in Perl :-)...
>
>#!/bin/sh
>
> Shell script removed

This will not work in all cases. 

In Gould's UTX/32 (4.3bsd based), some defines are hard-coded in /lib/cpp
(eg. gould, unix etc.) but others are passed on the command line used
by /bin/cc when it calls cpp (eg. -Dselport, -DCOFF).

Other systems may have the same problem. The shell script should
probably be modified to look for '-DXXX' in /bin/cc also.

Scott Williamson
scott@memex.co.uk