From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: "William J. Earl" <wje@cthulhu.engr.sgi.com>,
SGI Linux Alias <linux@cthulhu.engr.sgi.com>
Subject: Re: Include coherency problem, sigaction and otherwise
Date: Sat, 18 Mar 2000 01:08:01 -0300 [thread overview]
Message-ID: <20000318010801.B811@uni-koblenz.de> (raw)
In-Reply-To: <000e01bf903e$a0e864a0$0ceca8c0@satanas.mips.com>
On Fri, Mar 17, 2000 at 07:28:38PM +0100, Kevin D. Kissell wrote:
> > > 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.
> ...
> >
> > As near as I can tell, at least for glibc-2.1.1-7, there
> >is not machine-dependent <bits/sigaction.h> for mips, so the
> >generic one is used, and the definitions are incompatible with the
> >MIPS ABI. The Linux kernel, on the other hand, is compatible with the
> >MIPS ABI. The cure is to supply a MIPS-specific <bits/sigaction.h>.
>
> It's worse than that - the "Hard Hat" 5.1 distribution that serves
> as the reference userland for most SGI/MIPS/Linux platforms
> doesn't even have a /usr/include/bits directory, which seems
> to have been a more recent invention.
The whole inconsistence was a stupid accident. Since apparently only very
little software was affected negativly (read: no known problems) we didn't
try to come up with some genious compatibility hacks but just fixed the
definitions the hard way. Current glibc snapshots and Linux kernels have
been fixed to use the same definitions. If not, mail me a brown paperbag.
The bits/ subdirectory was introduced for glibc 2.1.
Ralf
next prev parent reply other threads:[~2000-03-18 4:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-17 18:28 Include coherency problem, sigaction and otherwise Kevin D. Kissell
2000-03-18 4:08 ` Ralf Baechle [this message]
2000-03-18 4:41 ` William J. Earl
2000-03-18 4:59 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2000-03-18 19:59 Kevin D. Kissell
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-17 16:21 Kevin D. Kissell
2000-03-17 18:02 ` William J. Earl
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=20000318010801.B811@uni-koblenz.de \
--to=ralf@oss.sgi.com \
--cc=kevink@mips.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=wje@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