From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, Roland McGrath <roland@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix NPTL build on IA-64
Date: Tue, 02 Nov 2004 21:32:00 -0000 [thread overview]
Message-ID: <20041102213047.GV30497@sunsite.ms.mff.cuni.cz> (raw)
Hi!
After recent changes to smp.h NPTL on IA-64 no longer compiles
- __set_errno is not defined.
Here is a quick fix, though not sure if it wouldn't be better to just
#include <errno.h> in all sysdep.h headers that define INLINE_SYSCALL
macro (as there __set_errno is used).
2004-11-02 Jakub Jelinek <jakub@redhat.com>
* sysdeps/unix/sysv/linux/smp.h: Include errno.h.
--- libc/nptl/sysdeps/unix/sysv/linux/smp.h 24 Oct 2004 22:04:05 -0000 1.2
+++ libc/nptl/sysdeps/unix/sysv/linux/smp.h 2 Nov 2004 17:07:42 -0000 1.1.2.2
@@ -17,6 +17,7 @@
write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
Boston, MA 02111-1307, USA. */
+#include <errno.h>
#include <fcntl.h>
#include <string.h>
#include <sys/sysctl.h>
Jakub
reply other threads:[~2004-11-02 21:32 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=20041102213047.GV30497@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).