Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Guido Guenther <agx@gandalf.physik.uni-konstanz.de>
To: Andrew Clausen <clausen@melbourne.sgi.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: porting arcboot
Date: Tue, 11 Feb 2003 11:55:06 +0100	[thread overview]
Message-ID: <20030211105506.GA17935@merry> (raw)
In-Reply-To: <20030210223955.GF8408@pureza.melbourne.sgi.com>

On Tue, Feb 11, 2003 at 09:39:55AM +1100, Andrew Clausen wrote:
>  * 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 call glibc (in fact in can't since we don't link
arcboot against non PIC glibc). It calls arclib.
 -- Guido

  reply	other threads:[~2003-02-11 10:55 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
2003-02-10 10:03 ` Guido Guenther
2003-02-10 22:39   ` Andrew Clausen
2003-02-11 10:55     ` Guido Guenther [this message]
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=20030211105506.GA17935@merry \
    --to=agx@gandalf.physik.uni-konstanz.de \
    --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