From: kagel AT quasar DOT bloomberg DOT com
Date: Thu, 21 Nov 1996 16:47:41 -0500
Message-Id: <9611212147.AA05410@quasar.bloomberg.com >
To: timolmst AT cyberramp DOT net
Cc: djgpp AT delorie DOT com
In-Reply-To: <5701qm$mo4@newshost.cyberramp.net> (timolmst@cyberramp.net)
Subject: Re: <signal.h>
Reply-To: kagel AT dg1 DOT bloomberg DOT com

   Errors-To: postmaster AT bloomberg DOT com
   From: timolmst AT cyberramp DOT net
   Newsgroups: comp.os.msdos.djgpp
   Date: Wed, 20 Nov 1996 22:49:51 GMT
   Organization: CyberRamp.net, Dallas, TX (214) 340-2020/(817) 226-2020 for info
   Lines: 20
   Nntp-Posting-Host: pm1-14.cyberramp.net
   X-Newsreader: Forte Free Agent 1.0.82
   Dj-Gateway: from newsgroup comp.os.msdos.djgpp
   Content-Type: text
   Content-Length: 523

   HI!

   I am trying to port a unix application to dos. I am getting an error
   from GCC saying some labels are undefined. They are :

   SIGQUIT and SIGBUS

   Aparantley it expects to find these defined in <SIGNAL.H>. The
   <signal.h> file for the GCC with the DJGPP package doesn't define
   them. Does anybody know what they should be? Or, how to work around
   them?

   I have GCC 2.7.2 on my Linux system, and it doesn't define then
   either.

   I'd appreciate it if someone knows the answer to this one.

   Tim Olmstead
   timolmst AT cyberramp DOT net


You could probably safely define them as follows:

#define SIGQUIT SIGINT
#define SIGBUS SIGSEGV

The SIGQUIT signal is a stronger version of SIGINT (like Ctrl-break -vs- Ctrl-C).
SIGBUS and SIGSEGV are subtle shadings of different kinds of address errors.

-- 
Art S. Kagel, kagel AT quasar DOT bloomberg DOT com

A proverb is no proverb to you 'till life has illustrated it.  -- John Keats