From: Jim Gifford <maillist@jg555.com>
To: Linux MIPS List <linux-mips@linux-mips.org>
Subject: MIPS64 NPTL Status
Date: Wed, 21 Sep 2005 22:12:21 -0700 [thread overview]
Message-ID: <43323D35.9030905@jg555.com> (raw)
Looking through the latest glibc snapshot they have removed linuxthreads
and moved it to ports. I know Daniel has been working on getting NPTL to
work on MIPS32, which it does. Thank you Daniel. I know from emails I
read around linux-mips.org he was going to work on MIPS64 NPTL, just
curious to the status.
For the record the current glibc snapshot will not build at all under
MIPS64. Here is the error message I have received, still working on
getting it to build properly
In file included from ../sysdeps/mips/libc-tls.c:20:
../sysdeps/generic/libc-tls.c: In function '__libc_setup_tls':
../sysdeps/generic/libc-tls.c:191: warning: implicit declaration of
function 'INTERNAL_SYSCALL_DECL'
../sysdeps/generic/libc-tls.c:191: error: 'err' undeclared (first use in
this function)
../sysdeps/generic/libc-tls.c:191: error: (Each undeclared identifier is
reported only once
../sysdeps/generic/libc-tls.c:191: error: for each function it appears in.)
../sysdeps/generic/libc-tls.c:191: warning: implicit declaration of
function 'INTERNAL_SYSCALL'
../sysdeps/generic/libc-tls.c:191: error: 'set_thread_area' undeclared
(first use in this function)
../sysdeps/generic/libc-tls.c:191: warning: implicit declaration of
function 'INTERNAL_SYSCALL_ERROR_P'
make[2]: *** [/mnt/lfs-mips64/build/glibc-cross-64bit/csu/libc-tls.o]
Error 1
make[2]: Leaving directory `/mnt/lfs-mips64/build/glibc-20050919/csu'
--
----
Jim Gifford
maillist@jg555.com
next reply other threads:[~2005-09-22 5:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 5:12 Jim Gifford [this message]
2005-09-22 20:38 ` MIPS64 NPTL Status John Connett
2005-09-22 20:44 ` Michael Uhler
2005-09-22 21:30 ` Daniel Jacobowitz
2005-09-22 22:28 ` Jim Gifford
2005-09-22 22:30 ` Daniel Jacobowitz
2005-09-26 15:17 ` Jim Gifford
2005-09-27 13:09 ` Daniel Jacobowitz
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=43323D35.9030905@jg555.com \
--to=maillist@jg555.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