From: "Kevin D. Kissell" <kevink@mips.com>
To: "Ralf Baechle" <ralf@oss.sgi.com>
Cc: "SGI Linux Alias" <linux@cthulhu.engr.sgi.com>
Subject: Re: Include coherency problem, sigaction and otherwise
Date: Sat, 18 Mar 2000 20:59:55 +0100 [thread overview]
Message-ID: <00aa01bf9114$8bc4b0c0$0ceca8c0@satanas.mips.com> (raw)
>> 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 ...)
I checked. 2.0.6-4 seems to be the same version as is in
the hardhat-sgi-5.1-tar.gz archive, and as such is broken.
Hope you're having a good flight!
Kevin K.
next reply other threads:[~2000-03-18 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-18 19:59 Kevin D. Kissell [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-18 11:57 Include coherency problem, sigaction and otherwise Kevin D. Kissell
2000-03-18 13:59 ` Ralf Baechle
2000-03-18 22:02 ` William J. Earl
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='00aa01bf9114$8bc4b0c0$0ceca8c0@satanas.mips.com' \
--to=kevink@mips.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@oss.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