From: Gary Thomas <gdt@linuxppc.org>
To: Duncan Grove <duncan@cs.adelaide.edu.au>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: modify /usr/include/signum.h
Date: Thu, 14 Jan 1999 10:43:43 -0000 (GMT) [thread overview]
Message-ID: <XFMail.990114104343.gdt@linuxppc.org> (raw)
In-Reply-To: <369D7A76.1FF003@cs.adelaide.edu.au>
On 14-Jan-99 Duncan Grove wrote:
>
> someone needs to add #define SIGCLD SIGCHLD to /usr/include/signum.h
>
> btw, why are so many of the /include/*.h files (esp. tcp code) so
> screwed? -- Why/how were they messed up for the PPC release from the
> original Redhat 5.2 distribution?
>
Mostly because they didn't come from the RedHat 5.2 distribution!
The majority of the ".h" files are part of the GLIBC package which
is now more than two years old.
This will be cleaned up, once the new GLIBC-2.1.xx packages are ready.
BTW - What do you mean "screwed" except for the plethora of warnings?
------------------------------------------------------------------------
Gary Thomas |
email: gdt@linuxppc.org | "Fine wine is a necessity of
... opinions expressed here are mine | life for me"
and no one else would claim them! |
| Thomas Jefferson
------------------------------------------------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-01-14 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-14 5:02 modify /usr/include/signum.h Duncan Grove
1999-01-14 10:43 ` Gary Thomas [this message]
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=XFMail.990114104343.gdt@linuxppc.org \
--to=gdt@linuxppc.org \
--cc=duncan@cs.adelaide.edu.au \
--cc=linuxppc-dev@lists.linuxppc.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).