From: torvalds@klaava.Helsinki.FI (Linus Torvalds) Subject: Re: Compiling TIN doesn't work Date: 7 Oct 1992 09:01:55 GMT
In article <Z0s7RB2w164w@field.ichaos.nullnet.fi> kkk@field.ichaos.nullnet.fi (Kristo Kaarlo Matias) writes:
>My porting saga continues... Now it's TIN 1.1 PL1. "make sysv" produces
>this:
>
>signal.c: In function 'set_signal_handlers':
>signal.c:45: 'SIGBUS' undeclared (first use this function)
>[...]
>signal.c: In function 'signal_handler':
>signal.c:102: 'SIGBUS' undeclared (first use this function)
>
>What the heck is this 'SIGBUS'? I didn't found it at /usr/include/*.
Argghh. This comes up every once in a while (about twice a day to be
exact), and the answer is that tin is not posix, and uses an obsolete
signal that linux doesn't use, but which exists under both sysV and bsd,
so most sources don't seem to bother checking about it.
The thing to do is to search for SIGBUS in the sources, and put a
#ifdef SIGBUS
...
#endif
around the offending code. It *could* be solved by adding a dummy
signal value to /usr/include/signal.h ("#define SIGBUS 31" or similar),
but the problem isn't really in the linux code but in the sources that
assume SIGBUS is defined.
>I have Linux 0.98 and GCC 2.2.2d. I compiled TIN with -DPOSIX_JOB_CONTROL,
>is this ok?
POSIX_JOB_CONTROL is ok.
Linus