Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: SGI Linux Alias <linux@cthulhu.engr.sgi.com>
Subject: Re: Include coherency problem, sigaction and otherwise
Date: Sat, 18 Mar 2000 10:59:24 -0300	[thread overview]
Message-ID: <20000318105924.A5581@uni-koblenz.de> (raw)
In-Reply-To: <005901bf90d1$269b2690$0ceca8c0@satanas.mips.com>

On Sat, Mar 18, 2000 at 12:57:29PM +0100, Kevin D. Kissell wrote:

> Having two independent sets of include files between kernel and userland
> is always a bad idea, but is not *necessarily* broken, and sometimes
> cannot be avoided.   The problem is not that the definitions are seperately
> wired, but that they are incompatible - the risk one takes when one creates
> multiple independent definitions.

The problem before that was that using the kernel headers for userland was
a serious problem.

> >                                     Current glibc snapshots and Linuxkernels
> have
> >been fixed to use the same definitions.  If not, mail me a brown paperbag.
> 
> Certainly the hardhat-sgi-5.1-tar.gz archive on oss.sgi.com is out of sync
> with any MIPS/Linux kernel sources of which I am aware.  The most recent
> version of glibc 2.0 for MIPS that I have been able to find is 2.0.7, and it
> too seems to be out of synch.  Which version of glibc has been fixed,
> and where can I download it?   Which userland distribution is built with
> the consistent glibc?

Definately no entire distribution, I'm also not sure if I actually did
publish a fixed libc due to another binutils related issue.  I'm about to
jump into a plane but could you take a look at
pub/linux/mips/redhat/manhattan/RedHat/RPMS/glibc-2.0.6-4.mipseb.rpm
from oss?

  Ralf  (Up, up and away ...)

  reply	other threads:[~2000-03-18 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-18 11:57 Include coherency problem, sigaction and otherwise Kevin D. Kissell
2000-03-18 13:59 ` Ralf Baechle [this message]
2000-03-18 22:02 ` William J. Earl
  -- strict thread matches above, loose matches on Subject: below --
2000-03-18 19:59 Kevin D. Kissell
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-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=20000318105924.A5581@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=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