Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Clausen <clausen@melbourne.sgi.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>, Guido Guenther <agx@sigxcpu.org>
Subject: Re: porting arcboot
Date: Mon, 10 Feb 2003 09:23:57 +0000	[thread overview]
Message-ID: <20030210092357.A879@linux-mips.org> (raw)
In-Reply-To: <20030210034549.GA8408@pureza.melbourne.sgi.com>; from clausen@melbourne.sgi.com on Mon, Feb 10, 2003 at 02:45:49PM +1100

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

  reply	other threads:[~2003-02-11 11:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10  3:45 porting arcboot Andrew Clausen
2003-02-10  9:23 ` Ralf Baechle [this message]
2003-02-10 10:03 ` Guido Guenther
2003-02-10 22:39   ` Andrew Clausen
2003-02-11 10:55     ` Guido Guenther
2003-02-11 22:46     ` Florian Lohoff
2003-02-12  5:03       ` Andrew Clausen
2003-02-12  8:21         ` Guido Guenther
2003-02-12 15:26         ` Florian Lohoff
2003-02-12 22:58           ` Andrew Clausen
2003-02-13  8:10             ` Florian Lohoff
2003-02-10 10:33 ` Vivien Chappelier
2003-02-10 11:13   ` Guido Guenther
2003-02-10 11:26     ` Guido Guenther
2003-02-10 11:26       ` Guido Guenther
  -- strict thread matches above, loose matches on Subject: below --
2003-02-10 12:50 Vivien Chappelier
2003-02-10 14:37 Vivien Chappelier
2003-02-10 15:01 ` Juan Quintela
2003-02-10 15:03   ` Christoph Hellwig
2003-02-10 15:14     ` Juan Quintela
2003-02-10 15:23       ` Guido Guenther

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=20030210092357.A879@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=agx@sigxcpu.org \
    --cc=clausen@melbourne.sgi.com \
    --cc=linux-mips@linux-mips.org \
    /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