From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix sparc64
Date: Mon, 02 Oct 2006 18:26:00 -0000 [thread overview]
Message-ID: <20061002182637.GH4556@sunsite.mff.cuni.cz> (raw)
Hi!
NPTL fails to build on sparc64, as ptw-pause.os needs __sigprocmask,
which is only defined in libc.so (and not exported), but not in
libpthread.so.
I guess the easiest fix is just to inline the call instead of ensuring
sigprocmask.os is linked into libpthread.so.
2006-10-02 Jakub Jelinek <jakub@redhat.com>
[BZ #3291]
* sysdeps/unix/sysv/linux/sparc/sparc64/pause.c: Include
errno.h, signal.h, unistd.h and sysdep-cancel.h.
(__sigprocmask): Define.
--- libc/sysdeps/unix/sysv/linux/sparc/sparc64/pause.c.jj 2006-08-22 10:42:34.000000000 +0200
+++ libc/sysdeps/unix/sysv/linux/sparc/sparc64/pause.c 2006-10-02 20:08:42.000000000 +0200
@@ -1 +1,9 @@
+#include <errno.h>
+#include <signal.h>
+#include <unistd.h>
+#include <sysdep-cancel.h>
+
+#define __sigprocmask(how, set, oset) \
+ INLINE_SYSCALL (rt_sigprocmask, 4, how, set, oset, _NSIG / 8)
+
#include <sysdeps/posix/pause.c>
Jakub
reply other threads:[~2006-10-02 18:26 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=20061002182637.GH4556@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).