linux-mips
[Top] [All Lists]

Re: HELP can't boot

To: Ian <ian@WPI.EDU>
Subject: Re: HELP can't boot
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Thu, 9 Aug 2001 04:31:08 +0200
Cc: Guido Guenther <guido.guenther@gmx.net>, linux-mips <linux-mips@oss.sgi.com>
In-reply-to: <Pine.OSF.4.33.0108082125510.29716-100000@grover.WPI.EDU>; from ian@WPI.EDU on Wed, Aug 08, 2001 at 09:27:17PM -0400
References: <20010808223940.B12550@galadriel.physik.uni-konstanz.de> <Pine.OSF.4.33.0108082125510.29716-100000@grover.WPI.EDU>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Mutt/1.2.5i
On Wed, Aug 08, 2001 at 09:27:17PM -0400, Ian wrote:

> > Try just "bootp():". The prom is clever enough to figure out the rest.
> 
> Doesn't work.  It complains that Sash is missing.
> 
> > I doubt that. You can't compile a recent glibc with that outdated toolchain.
> 
> You can.  You just build glibc and gcc with the old gcc (2.7.8?), and then
> you chroot into the newly-built environment and rebuild it again with the
> new gcc.

Since Hardhat there have been various places in the kernel, libc and tools
where for the sake of sanity and bugfixes we had to break the binary
compatibility.  Add the rest of bugs and you'll find probably have an
interesting even impossible job to upgrade.

Certain packages such as rpm can only sanely be upgraded by upgrading from
a binary package as any attempt to rebuild would automatically inherit
the broken settings of the installed package.  Oh and a rebuild of a
current distribution should need about 3 days of CPU or so ...

  Ralf

<Prev in Thread] Current Thread [Next in Thread>