From: Jeff Blank <jfblank@mtu.edu>
To: zsh-workers@math.gatech.edu
Subject: signames.h (Solaris 2.4)
Date: Mon, 25 Sep 1995 16:43:20 -0400 (EDT) [thread overview]
Message-ID: <199509252043.QAA10697@bullwinkle.tc.mtu.edu> (raw)
I remember that there's been discussion of signames.h and the SIGCOUNT
macro on this list...but not having had any problems, I didn't pay much
attention. Now I might be having a problem. =) I'm building 2.6-beta10 on
a Solaris 2.4 machine. My SIGCOUNT is 43, and I can't quite remember
whether that's the correct value. Could somebody clue me in?
Thanks,
Jeff
--
"Instead of trying to build newer and | Jeff Blank
bigger weapons of destruction, we | MTU IT/Telcom
should be thinking about getting more | jfblank@mtu.edu
use out of the ones we already have." | http://pace1.cts.mtu.edu:8080/~jfblank
--Jack Handey
next reply other threads:[~1995-09-25 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-25 20:43 Jeff Blank [this message]
1995-09-25 21:11 ` Richard Coleman
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=199509252043.QAA10697@bullwinkle.tc.mtu.edu \
--to=jfblank@mtu.edu \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).