Re: Signal names with autoconf?

[David Masterson]

Nearly missed this...

Afraid this is not something I've seen before.  Thanks for the vote of
confidence, Mark, but I'm not that good.  :-(

p.s. Maybe the stringize operator ('#') would help here?

>>>>> Mark Burgess writes:

> I bet David Masterson would know if autoconf could be used to
> extract the signal names for each OS and build a table?
> David?

> Mark


> On 23 Apr, Michael Beattie wrote:
>> On Mon, Apr 22, 2002 at 05:13:07PM -0700, Tim Auckland wrote:
>>> signal.h does not give you the strings for the signal names, just the
>>> #defines for the numbers.  You have to put in a bit more work to get the
>>> string-to-number mapping, but it's still do-able.
>>> 
>>> Something like:
>> ...
>>> although there's probably a neater way.
>>> 
>>> Cfengine also uses an enum somewhere in the signal name mapping code,
>>> which would have to be dealt with similarly.
>> 
>> 
>> How about just using the #define's to give the right signal, when the
>> name is used?
>> 
>> signal = hup
>> 
>> wherever it parses that, use SIGHUP. Then you can map symbolic names
>> cfengine style, to SIGxxx #define values.
>> 
>> I would have thought that was the sensible method.
>> 
>> If I sound incoherent, thats because I usually am.
>> 
>> Mike.



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



-- 
David Masterson                David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA