From: "Kevin D. Kissell" <kevink@mips.com>
To: "SGI Linux Alias" <linux@cthulhu.engr.sgi.com>
Subject: Include coherency problem, sigaction and otherwise
Date: Fri, 17 Mar 2000 17:21:29 +0100 [thread overview]
Message-ID: <00b801bf902c$ddb30140$0ceca8c0@satanas.mips.com> (raw)
Invesitgating some non-fatal but odd behaviour, we
have traced it to the fact that the defintions of various
sigaction flags are defined for MIPS/Linux user code
in /usr/include/sigaction.h, but defined for the kernel in
/usr/include/asm/signal.h, and that the two definitions
are not consistent. Does anyone know how this
came about?
I have the impresson that the /usr/include stuff in the
"Hard Hat" distribution for MIPS is keyed to a 2.0.x kernel,
and that an update of /usr/include (as opposed to a downgrade
of the kernel headers) may be in order. Frankly, I don't like
the fact that the user and kernel includes don't pull everything
out of common files in include/linux and include/asm - I suppose
it must have been to reduce the number of compilations
that depend on kernel includes - but I don't see that
we can do much about that from here in MIPS-land.
__
Kevin D. Kissell
MIPS Technologies European Architecture Lab
kevink@mips.com
Tel. +33.4.78.38.70.67
FAX. +33.4.78.38.70.68
next reply other threads:[~2000-03-17 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-17 16:21 Kevin D. Kissell [this message]
2000-03-17 18:02 ` Include coherency problem, sigaction and otherwise William J. Earl
-- strict thread matches above, loose matches on Subject: below --
2000-03-17 18:28 Kevin D. Kissell
2000-03-18 4:08 ` Ralf Baechle
2000-03-18 4:41 ` William J. Earl
2000-03-18 4:59 ` Ralf Baechle
2000-03-18 11:57 Kevin D. Kissell
2000-03-18 13:59 ` Ralf Baechle
2000-03-18 22:02 ` William J. Earl
2000-03-18 19:59 Kevin D. Kissell
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='00b801bf902c$ddb30140$0ceca8c0@satanas.mips.com' \
--to=kevink@mips.com \
--cc=linux@cthulhu.engr.sgi.com \
/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