Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Jim Gifford <maillist@jg555.com>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: Building o32 glibc on mips64
Date: Mon, 13 Jun 2005 15:56:02 -0400	[thread overview]
Message-ID: <20050613195602.GA3739@nevyn.them.org> (raw)
In-Reply-To: <42AB3366.8030206@jg555.com>

On Sat, Jun 11, 2005 at 11:54:30AM -0700, Jim Gifford wrote:
> Anyone got any ideas on how to fix this. I'm using binutils 2.16, gcc 
> 3.4.4, and glibc-2.3.5 with the syscall patch. Looks like socket.S is 
> not being generated.

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.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-06-13 19:56 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 [this message]
2005-06-13 20:05   ` Maciej W. Rozycki
2005-06-13 20:08     ` Christoph Hellwig
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=20050613195602.GA3739@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@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