From: culliton@srg.af.mil (Tom Culliton x2278)
To: rsalz@osf.org
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: RC on HP9000/710?
Date: Fri, 16 Apr 1993 11:16:01 -0400 [thread overview]
Message-ID: <9304161116.aa01178@ceres.srg.af.mil> (raw)
Rich says:
> Tnx for the note. I think run-time lookup isn't going to cost a lot...
It would be more robust at a minor run time cost, but that just masks
the problem. At the base of it is the fact that the mksignal script
gets confused if sys/signal.h is not relatively simple. We need a way
to detect this at compile time.
Tom
next reply other threads:[~1993-04-16 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-16 15:16 Tom Culliton x2278 [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-04-16 14:48 Tom Culliton x2278
[not found] <Sm@cerberus.bhpese.oz.au>
1993-04-16 11:49 ` rsalz
1993-04-15 14:05 rsalz
1993-04-15 23:33 ` Scott Merrilees
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=9304161116.aa01178@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=rsalz@osf.org \
/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).