From: "Kevin D. Kissell" <kevink@mips.com>
To: Ian Chilton <ian@ichilton.co.uk>
Cc: pete <pete@blackhammer.com>, linux-mips@oss.sgi.com
Subject: Re: MIPS linux
Date: Wed, 08 Nov 2000 12:03:11 -0800 [thread overview]
Message-ID: <3A09B17F.7FF3B03B@mips.com> (raw)
In-Reply-To: 20001108185711.A10689@woody.ichilton.co.uk
Ian Chilton wrote:
>
> Hello,
>
> > and noticed that you do not recommend using the hardhat distro based on
>
> You can use it, but it is old and broken. It will get you booted into Linux, but IIRC you can not even compile a kernel :(
Sure you can! I've done it hundreds of times. ;-)
You can even build binutils. But you can't
build gcc, and any application that depends
on certain subtleties of signal behavior will be
betrayed by the discrepancy between the
HardHat glibc and the 2.2-3-4 kernels.
So I too am eagerly looking forward to
a 6.0 or 7.0 based solution - provided that
the glibc disconnects are fixed as well.
Kevin K.
next prev parent reply other threads:[~2000-11-08 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 18:57 MIPS linux Ian Chilton
2000-11-08 20:03 ` Kevin D. Kissell [this message]
2000-11-08 22:26 ` J. Scott Kasten
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=3A09B17F.7FF3B03B@mips.com \
--to=kevink@mips.com \
--cc=ian@ichilton.co.uk \
--cc=linux-mips@oss.sgi.com \
--cc=pete@blackhammer.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