Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com, linux-mips@fnet.fr, debian-mips@lists.debian.org
Subject: glibc on MIPS ...
Date: Tue, 10 Oct 2000 19:30:16 -0700	[thread overview]
Message-ID: <39E3D0B8.7F221344@mvista.com> (raw)


Does anybody what is the status of glibc on MIPS?

So far I have been using the glibc coming from linux-vr project.  It is
v2.0.7.  Somehow the pthread does not appear to be working. 
pthread_create() returns EAGIN error, even though clone() system returns
correct result.

I looked at the cvs tree on oss.sgi.com.  The glibc version is 2.0.6. 
What is the status of this version?

I also heard about the debian-mips project.  What glibc is used here?

Thanks.

Jun

             reply	other threads:[~2000-10-10 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11  2:30 Jun Sun [this message]
2000-10-11  2:12 ` glibc on MIPS Ralf Baechle
2000-10-11 11:06   ` Maciej W. Rozycki
2000-10-11 22:24   ` Florian Lohoff
2000-10-12  2:04     ` Ralf Baechle

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=39E3D0B8.7F221344@mvista.com \
    --to=jsun@mvista.com \
    --cc=debian-mips@lists.debian.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.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