linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Florian Lohoff <flo@rfc822.org>,
	linux-mips@oss.sgi.com, linux-mips@fnet.fr,
	linux-origin@oss.sgi.com
Subject: Re: libc upgrade
Date: Tue, 26 Sep 2000 12:30:03 +0400	[thread overview]
Message-ID: <39D05E8B.A7F4A2D9@niisi.msk.ru> (raw)
In-Reply-To: 20000925221414.A6190@bacchus.dhis.org

Ralf,

BTW, what should we use as system headers with glibc nowadays ? Should
it be old HardHat kernel-headers-2.1.100 or newer 2.2.x ?

> I week of CPU time on an Origin building packages:  No problems ...  I'm
> actually fairly close to get a RH 6.2 built - as far as that is possible
> with glibc 2.0.
> 

Do you have the packages somewhere on the net ? I am personally
interested in disk packages (fdisk, msdostools &co.) and the packages
required in order to run 2.2 kernels. Old HardHat cfdisk, for example,
seems to create partitions in the big endian format. At least, the rest
see garbage after cfdisk creates a partition table.

Regards,
Gleb.

  parent reply	other threads:[~2000-09-26  8:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-22 13:26 libc upgrade Ralf Baechle
2000-09-25  9:24 ` Florian Lohoff
2000-09-25 11:20   ` Ralf Baechle
2000-09-25 14:15     ` Florian Lohoff
2000-09-25 20:14       ` Ralf Baechle
2000-09-25 23:04         ` Florian Lohoff
2000-09-26  0:46           ` Ralf Baechle
2000-09-26  8:37           ` Gleb O. Raiko
2000-09-26 10:36             ` Florian Lohoff
2000-09-26 21:06               ` Ralf Baechle
2000-09-26 17:48             ` Keith M Wesolowski
2000-09-26  8:30         ` Gleb O. Raiko [this message]
2000-09-26 22:47           ` Ralf Baechle

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=39D05E8B.A7F4A2D9@niisi.msk.ru \
    --to=raiko@niisi.msk.ru \
    --cc=flo@rfc822.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=linux-origin@oss.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;
as well as URLs for NNTP newsgroup(s).