linux-mips
[Top] [All Lists]

Re: porting arcboot

To: Guido Guenther <agx@gandalf.physik.uni-konstanz.de>
Subject: Re: porting arcboot
From: Andrew Clausen <clausen@melbourne.sgi.com>
Date: Tue, 11 Feb 2003 09:39:55 +1100
Cc: Linux-MIPS <linux-mips@linux-mips.org>
In-reply-to: <20030210100319.GA30624@merry>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030210034549.GA8408@pureza.melbourne.sgi.com> <20030210100319.GA30624@merry>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4i
On Mon, Feb 10, 2003 at 11:03:19AM +0100, Guido Guenther wrote:
> E2fslib will move out of arcboot with the next release and arcboot will
> link against the non pic version in the debian archive. I'd really like
> to keep e2fslib out of arcboot (at least for the debian version which is
> quiet different from the oss.sgi.com version).

Ah, ok.  Now we're just stuck with the problem that we can't build
e2fsprogs for misp64, since we don't have the toolchain for it.

e2fsprogs looks like it resists cross-compiling also :(

So, the obstacles are:
 * e2fsprogs uses libc headers quite extensively, but there is no
glibc available for mips64 (right?).  It also seems to make quite a
few libc calls?  (How are you planning to deal with that?  Link
against it statically?  What about syscalls?)
 * e2fsprogs doesn't use autoconf/automake "properly".  It doesn't seem
to support cross-compiling.  Adding cross-compile support looks
somewhat non-trivial, since it builds it's own tools to compile itself.
(A fancy sed replacement, for some reason?)
 * there is no toolchain to build e2fsprogs on mips64 cleanly... need
to do that objcopy business.  This means hacking the build process?

> There should't be many
> libc header dependencies left then. If there are still any I'd be happy
> to kill them.

:)

Cheers,
Andrew


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