Path: utzoo!attcan!craig
From: craig@attcan.UUCP (Craig Campbell)
Newsgroups: comp.sources.d
Subject: Re: Comments on ABC problems by the authors
Message-ID: <13368@vpk4.UUCP>
Date: 4 Jan 91 14:42:05 GMT
References: <2747@charon.cwi.nl>
Reply-To: craig@vpk4.ATT.COM (Craig Campbell)
Organization: AT&T Canada Inc., Toronto
Lines: 44

In article <2747@charon.cwi.nl> timo@cwi.nl (Timo Krijnen) writes:
 
>2) Setup and Unixes.
>Setup tries to find out what type of Unix you are running. After it
>was written (years ago:-) most unixes got "enhanced". Some
>SystemV-look-alikes added BSD-isms and vice versa. We have a new
>version which no longer uses SIGCLD and SIGCHLD, but instead tries to
>discriminate between BSD-types with SIGXCPU and VTALRM and checks for
>System V with SIGPWR. But it uses this only as a suggestion, leaving
>the ultimate choice to the installer herself.
 
>-- 
> Timo Krijnen
> CWI (Center for Math. & Comp. Science), Amsterdam
> timo@cwi.nl

Timo, there is what might be considered a better way to determine what type of
system a given package is being compiled on.  That is, the reserved defined 
symbols in cpp(1).  For example:

System			Symbols Defined By cpp(1)

AT&T 3B2		unix u3b2
AT&T 3B5		unix u3b5
AT&T 6386		unix i386
AT&T 6486		unix i386   (Oh well, it's still in CI)

etc....

I beleive most (hopefully all) vendors have defines for their unique
systems in their cpp(1) program.  I do not have available other vendors
systems at this time, however, so I cannot verify that or list the defines.
Perhaps other netters could fill you in about these.

If these defines are used to select Berkley/Sys V then hopefully, checking
include files, which may change, will be unnecessary.


Hope this is helpful,
(It really does make porting easier...)

craig