Re: Signal names with autoconf?

[Michael Beattie]

On Tue, Apr 23, 2002 at 12:52:11PM +0200, address@hidden wrote:
> Sorry, but this is nonsense. You haven't been following
> the discussion.

Bullshit Mark, I've been following it from the first post.

> 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

There is such a thing as POSIX - I'm not sure if this is covered in
it, since I have not shelled out for the spec.


address@hidden:~> uname -s
Linux
address@hidden:~> grep signum /usr/include/signal.h
#include <bits/signum.h>


$ uname -s
SunOS
$ grep signal.h /usr/include/signal.h
#include <sys/signal.h>


> 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.

Um, The whole Idea of headers is that they'll be processed, by the C
Pre Processor.

Dont use autoconf to do it, there is no need.

I dont understand why you cant just include the header, and use the SIG*
definitions. No need to clutter auto* with that.

Why do you need a table? Ok, I admit, I have not looked at the code for
the signal stuff, *yet*. but if you need a table, you can just use the
symbolic name and the #define'd value. "hup" and SIGHUP for example.

Instead of telling me this is nonsense, correct me. or give me a good
reason to shut up ;)

Mike.
-- 
Michael Beattie <address@hidden>