From: Ralf Baechle <ralf@oss.sgi.com>
To: "Gleb O. Raiko" <raiko@niisi.msk.ru>
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: Wed, 27 Sep 2000 00:47:22 +0200 [thread overview]
Message-ID: <20000927004722.B8644@bacchus.dhis.org> (raw)
In-Reply-To: <39D05E8B.A7F4A2D9@niisi.msk.ru>; from raiko@niisi.msk.ru on Tue, Sep 26, 2000 at 12:30:03PM +0400
On Tue, Sep 26, 2000 at 12:30:03PM +0400, Gleb O. Raiko wrote:
> 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 ?
Definately not the old hardhat kernel headers. I'm using 2.2 header and
recommend doing the same for best success with packages for current
distributions based on this kernel. Building some packages may actually
require a newer version but in general the lastest 2.2 headers are the
best.
> > 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.
I've got a hacked utils-linux package, I think it's in the redhat-6.0
packages that are on oss. I don't really intend to upload all the stuff
to oss, they're just a big test for the changed compile environment which
I'm using, that is binutils-current and gcc-current. Before I even fiddle
with stuff like glibc 2.2 etc. I want to know that the tools are reasonably
solid. So far they seem to be good after applying a few minor but essential
patches. Still need to test building a kernel.
Ralf
prev parent reply other threads:[~2000-09-26 22:48 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
2000-09-26 22:47 ` Ralf Baechle [this message]
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=20000927004722.B8644@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=flo@rfc822.org \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=linux-origin@oss.sgi.com \
--cc=raiko@niisi.msk.ru \
/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