From: Vincent Broman <broman@nosc.mil>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc-1.5b3 nearly ready for release
Date: Thu, 19 Feb 1998 20:08:42 -0500 [thread overview]
Message-ID: <19980220010842.6104.qmail@np.nosc.mil> (raw)
In-Reply-To: <aAUAAJF07DQ7pggA@nan.cygnus.co.uk> (message from Tim Goodwin on Thu, 19 Feb 1998 18:05:48 +0000)
-----BEGIN PGP SIGNED MESSAGE-----
I tried out the nearly-rc-1.5b3 on sparc-sun-sunos413 with gcc
and it was OK except for one thing, the prototype for stat() in which.c
conflicts with that supplied by Sun, which lacks a "const".
I would suppose the prototype would belong in "sys/stat.h".
If we do need a declaration in which.c, it could be
no more than "extern int stat();".
The vanilla source compiles and trips fine on Debian GNU/Linux 1.3.1,
with gcc 2.7.2.1, libc 5.4.33, and kernel 2.0.33, except that
strangely enough "cat" writes its error message "cat: -: Bad file number"
twice in a row. It seems to be cat's problem.
It might be nice if make distclean did not remove y.tab.?
in the case where byacc is not available.
The BUILT_SOURCES macro doesn't seem to include sigmsgs.h or y.tab.h .
The whole approach of grepping in signal.h for signal names and meanings
is inherently fragile and unnatural. Based on a suggestion from the
Debian developers group, I quickly hacked together an auxillary C program
now found at http://archimedes.nosc.mil/transfer/mksignals.c
which checks by means of #ifdef for all the signal names found on machines
I have access to and writes out the sigmsgs.* files directly.
This means that mksignal could be replaced by mksignals.c,
with Makefile lines like these.
mksignals: $(srcdir)/mksignals.c
$(CC) $(srcdir)/mksignals.c -o mksignals
sigmsgs.c sigmsgs.h: mksignals
./mksignals
A "make clean" should also remove the executable, mksignals.
The list of signal names could be easily expanded to included
any special signals defined on machines other than my own stable of:
linux, sunos, solaris, next, hpux, and os/2 emx.
Vincent Broman, code D712 Bayside
Space and Naval Warfare Systems Center, San Diego (was NOSC, NRaD)
San Diego, CA 92152-6145, USA Phone: +1 619 553 1641
Email: broman at spawar.navy.mil or nosc.mil PGP protected mail preferred.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNOzXg2CU4mTNq7IdAQH/mgQAvDPTyjtvWySqmvQhzv8+6Q88obrdrmwq
PK3NI3LtL5mBYGWF2hi0vxzb6srPd+rUN6O/I+uTSJzhx7UUCAAIfi9qstSYdfj1
ndR2N9wcodZY+BsTHP04rLQBm+qjwjLSE66Flki7+Hfz1ZtuX7JgQ6T4v6gYGF3a
XHMKcp/DVpE=
=/80D
-----END PGP SIGNATURE-----
parent reply other threads:[~1998-02-21 3:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <aAUAAJF07DQ7pggA@nan.cygnus.co.uk>]
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=19980220010842.6104.qmail@np.nosc.mil \
--to=broman@nosc.mil \
--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).