linux-mips
[Top] [All Lists]

Re: porting arcboot

To: Andrew Clausen <clausen@melbourne.sgi.com>
Subject: Re: porting arcboot
From: Ralf Baechle <ralf@linux-mips.org>
Date: Mon, 10 Feb 2003 09:23:57 +0000
Cc: Linux-MIPS <linux-mips@linux-mips.org>, Guido Guenther <agx@sigxcpu.org>
In-reply-to: <20030210034549.GA8408@pureza.melbourne.sgi.com>; from clausen@melbourne.sgi.com on Mon, Feb 10, 2003 at 02:45:49PM +1100
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030210034549.GA8408@pureza.melbourne.sgi.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5.1i
On Mon, Feb 10, 2003 at 02:45:49PM +1100, Andrew Clausen wrote:

> I'm planning to try porting arcboot to ip27 (mips64).
> 
> I plan to do this by cross-compiling... this is actually the only
> option since there's no 64 bit userland yet.
> 
> Some issues:
> 
>  * I'll be cross-compiling (using the mips64-linux-gcc & friends that
> are provided on ftp.linux-mips.org), which means some makefile hacking...
> 
>  * there's no mips64-linux glibc, which means no libc headers are
> available.  So I need to either cut&paste libc headers, or remove
> dependencies on them.  This affects lots of code.
> 
>  * the e2fs stuff... how is this being maintained?  It uses libc
> headers a bit... can I kill them?  Or will this make it hard to update
> to new upstream e2fsprogs releases?
> 
> Anything else?

Arcboot is a standalone program.  As such it shouldn't use anything from
glibc or it's going to be a royal pain in the lower back extension.
Look at Milo, spit and say no.  So keeping a private copy of the necessary
headers is the only sane way to get things to work.

  Ralf

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