RE: Signal names with autoconf?

[Tim Auckland]

The "bash" comment was because bash's implementation if kill -l gives
the signal numbers as well, so I could use it to generate the table
directly.  Traditional kill -l does not give the numbers, but it still
gives a useful way of finding out the available names if you need that.

Bash itself generates the list at compile-time by trying a long list of
signal names and seeing if they are defined on that platform.

Tim

> -----Original Message-----
> From: Darrell Fuhriman [mailto:address@hidden 
> Sent: Tuesday, April 23, 2002 9:20 AM
> To: David Masterson
> Cc: address@hidden
> Subject: Re: Signal names with autoconf?
> 
> 
> > Stringize it?
> 
> OK, everyone, you're making this really, really too hard.  
> 'kill -l' does
> *not* need to depend on bash.
> 
> % uname -svr
> SunOS 5.8 Generic_108528-13
> 
> % /usr/bin/kill -l
> 
> EXIT HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS 
> PIPE ALRM TERM USR1 USR2 CLD PWR WINCH URG POLL STOP TSTP 
> CONT TTIN TTOU VTALRM PROF XCPU XFSZ WAITING LWP FREEZE THAW 
> CANCEL LOST RTMIN RTMIN+1 RTMIN+2 RTMIN+3 RTMAX-3 RTMAX-2 
> RTMAX-1 RTMAX 
> 
> If that's still not portable enough for you, why not just 
> hack the code that comes with the Configure script in perl?
> 
> Why are we trying to reinvent the wheel?
> 
> Darrell
> 
> 
> 
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden http://mail.gnu.org/mailman/listinfo/bug-cfengine
>