Re: Signal names with autoconf?

[Mark . Burgess]

Sorry, but this is nonsense. You haven't been following
the discussion. First you have to find where the #defines are,
and they are almost never in anything so obvious as signal.h

solaris: sys/signal.h
linux: bits/signum.h

etc etc

Then you need to process that file somehow to extract the
name/number association and get it into a table. I was asking
whether autoconf's expert knowledge and tools could make
this easy.

Mark

On 23 Apr, Michael Beattie wrote:
> On Tue, Apr 23, 2002 at 07:31:56AM +0200, address@hidden wrote:
>> 
>> I bet David Masterson would know if autoconf could be used to
>> extract the signal names for each OS and build a table?
>> David?
> 
> No no no no no.
> 
> signal.h includes the relevant headers one way or another to give you
> the definitive #define's.  Include signal.h, and you're set..
> 
> Take signal.h, follow its #includes.
> 
> Mike.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~