Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: uclibc@uclibc.org, linux-mips@linux-mips.org
Subject: NPTL uClibc status update...
Date: Tue, 30 Aug 2005 00:11:01 -0500	[thread overview]
Message-ID: <4313EA65.7090306@realitydiluted.com> (raw)

Greetings.

Now that I have all my work up to date and checked in, I thought I would
give a brief status of NPTL. With the latest from 'uClibc-nptl' branch,
binutils-2.16.1 and gcc-4.1.0-20050604 a complete NPTL toolchain can be
built. This toolchain can also compile an entire buildroot. Granted, the
binaries will not run, but this means that the new NPTL libraries are
properly exporting all the symbols necessary for applications to build
and weak symbols interactions are doing what they should.

I am currently now building static test programs from glibc for uClibc to
get TLS binaries for MIPS working. Don't expect a lot of activity in the
upcoming days as I will be debugging all the problems with TLS on MIPS.
Thanks for your patience.

-Steve

                 reply	other threads:[~2005-08-30  5:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4313EA65.7090306@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=linux-mips@linux-mips.org \
    --cc=uclibc@uclibc.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