From: culliton@srg.af.mil (Tom Culliton x2278)
To: alan@jayg.astro.wisc.edu
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: FAQ system list
Date: Tue, 15 Jun 1993 22:27:13 -0400 [thread overview]
Message-ID: <9306152227.aa22056@ceres.srg.af.mil> (raw)
> i386/i486 SCO-ODT SVR3 gcc v2 [h][i]
> i386/i486 SCO-ODT SVR3 cc [h][i]
>
> [h] Requires intervention by hand to get mksignal to work,
> because of deficient sh, awk, etc.
> [i] See 4.13.
While I'm the first one to throw stones at SCO-ODT this needs to be
clarified. The problem is not a deficiency in SCO the utilities, but
rather a very complicated /usr/include/sys/signal.h with preprocessor
conditionals that end up defeating the scripts assumptions. If the
problem was with the utilities using gnu substitutes should fix it and
they don't.
Tom
BTW - attached is the hacked version of SCO's sys/signal.h that I use to
build a good rc.
------------------------------signal.hacked------------------------------
/* This is a hacked down version of /usr/include/sys/signal.h needed
* because mksignal has problems with preprocessor conditionals.
*/
#define SIGHUP 1 /* hangup */
#define SIGINT 2 /* interrupt (rubout) */
#define SIGQUIT 3 /* quit (ASCII FS) */
#define SIGILL 4 /* illegal instruction (not reset when caught)*/
#define SIGTRAP 5 /* trace trap (not reset when caught) */
#define SIGIOT 6 /* IOT instruction */
#define SIGABRT 6 /* used by abort, replace SIGIOT in the future */
#define SIGEMT 7 /* EMT instruction */
#define SIGFPE 8 /* floating point exception */
#define SIGKILL 9 /* kill (cannot be caught or ignored) */
#define SIGBUS 10 /* bus error */
#define SIGSEGV 11 /* segmentation violation */
#define SIGSYS 12 /* bad argument to system call */
#define SIGPIPE 13 /* write on a pipe with no one to read it */
#define SIGALRM 14 /* alarm clock */
#define SIGTERM 15 /* software termination signal from kill */
#define SIGUSR1 16 /* user defined signal 1 */
#define SIGUSR2 17 /* user defined signal 2 */
#define SIGCLD 18 /* death of a child */
#define SIGPWR 19 /* power-fail restart */
#define SIGWINCH 20 /* window change */
/* SIGPHONE only used in UNIX/PC */
/*#define SIGPHONE 21*/ /* handset, line status change */
#define SIGPOLL 22 /* pollable event occured */
#define SIGCHLD SIGCLD /* compatibility */
#define SIGSTOP 23 /* sendable stop signal not from tty */
#define SIGTSTP 24 /* stop signal from tty */
#define SIGCONT 25 /* continue a stopped process */
#define SIGTTIN 26 /* to readers pgrp upon background tty read */
#define SIGTTOU 27 /* like TTIN for output if (tp->t_local&TOSTOP) */
#define SIGALL (~(sigset_t)0L) /* new for POSIX */
#define NSIG 28 /* The valid signal number is from 1 to NSIG-1 */
#define MAXSIG 32 /* size of u_signal[], NSIG-1 <= MAXSIG*/
/* MAXSIG is larger than we need now. */
/* In the future, we can add more signal */
/* number without changing user.h */
next reply other threads:[~1993-06-16 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-06-16 2:27 Tom Culliton x2278 [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-06-18 10:57 Stefan Dalibor
[not found] <alan@oldp.astro.wisc.edu>
1993-06-16 17:38 ` malte
1993-06-16 17:41 ` Chris Siebenmann
1993-06-16 15:02 Alan Watson
1993-06-16 16:52 ` mycroft
1993-06-16 7:34 noel
1993-06-15 23:18 Alan Watson
1993-06-15 23:25 ` mycroft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9306152227.aa22056@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=alan@jayg.astro.wisc.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).