Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "William J. Earl" <wje@cthulhu.engr.sgi.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	"Kevin D. Kissell" <kevink@mips.com>,
	SGI Linux Alias <linux@cthulhu.engr.sgi.com>
Subject: Re: Include coherency problem, sigaction and otherwise
Date: Sat, 18 Mar 2000 01:59:43 -0300	[thread overview]
Message-ID: <20000318015943.A1536@uni-koblenz.de> (raw)
In-Reply-To: <14547.2292.467349.391271@liveoak.engr.sgi.com>

On Fri, Mar 17, 2000 at 08:41:24PM -0800, William J. Earl wrote:

>  > The bits/ subdirectory was introduced for glibc 2.1.
> 
>     The bits/ subdirectory is present in 2.1, but at least 2.1.1-7 does
> not have a bits/sigaction.h for MIPS in the source, so the generic 
> one is used, and that is inconsistent with the kernel.

2.1 isn't supposed to be usable or even compilable for MIPS thanks to the
infamous linker problems.  Details on request.

> Which source for glibc has a MIPS bits/sigaction.h?

The latest Cygnus CVS development version has this and many other buglets
corrected mostly thanks to Andreas Jaeger who did start integrating my
old 2.0 port with the GNU sources and fix a ton of such buglets.

  Ralf

  reply	other threads:[~2000-03-18  5:19 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
2000-03-18  4:41   ` William J. Earl
2000-03-18  4:59     ` Ralf Baechle [this message]
  -- 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=20000318015943.A1536@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