Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Daniel Jacobowitz <dan@debian.org>,
	Jim Gifford <maillist@jg555.com>,
	Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: Building o32 glibc on mips64
Date: Mon, 13 Jun 2005 22:08:20 +0200	[thread overview]
Message-ID: <20050613200820.GA29872@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506132100080.1725@blysk.ds.pg.gda.pl>

On Mon, Jun 13, 2005 at 09:05:59PM +0100, Maciej W. Rozycki wrote:
> On Mon, 13 Jun 2005, Daniel Jacobowitz wrote:
> 
> > I have not tried the 2.3.x series glibcs on MIPS64.  I recommend you
> > use glibc HEAD for now instead, unless you're interested in tracking
> > down this sort of problem.
> 
>  FYI, I've been able to build glibc 2.3.5 with GCC 4.0.0 for 
> mips64el-linux (n64) with minimal patching.  I think what's only really 
> required is that patch by Richard Sandiford that stays suspended in the 
> glibc Bugzilla.
> 
>  For o32 glibc may have to be configured for "mips{,el}-linux" (as o32 
> isn't MIPS64 at all), but that's a pure guess -- I haven't checked the 
> scripts for that requirement.
> 
>  Do you think HEAD is stable enough for a non-glibc developer?  It's soon 
> after a fork after all, so I'd expect more serious changes to be applied 
> nowadays.

Btw, what is the chance to see a biarch toolchain for mips?  It seems
all linux architectures with 32bit and 64bit variants seem to have one
these days, except mips.

  reply	other threads:[~2005-06-13 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-11 18:54 Building o32 glibc on mips64 Jim Gifford
2005-06-13 19:56 ` Daniel Jacobowitz
2005-06-13 20:05   ` Maciej W. Rozycki
2005-06-13 20:08     ` Christoph Hellwig [this message]
2005-06-13 20:18       ` Maciej W. Rozycki
2005-06-13 20:55       ` Daniel Jacobowitz
2005-06-14  8:00         ` Jim Gifford
2005-06-14 10:36           ` Richard Sandiford

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=20050613200820.GA29872@lst.de \
    --to=hch@lst.de \
    --cc=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=maillist@jg555.com \
    /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