From: Daniel Jacobowitz <dan@debian.org>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: 2.5 n32 syscall numbers are wrong
Date: Tue, 23 Dec 2003 12:57:32 -0500 [thread overview]
Message-ID: <20031223175732.GA26052@nevyn.them.org> (raw)
If you take a look at scall64-n32.S, you'll find that there's no hole after
sendfile64. But in <asm/unistd.h> there is. So glibc gets built with the
wrong number for clock_gettime and confusion ensues...
Index: unistd.h
===================================================================
RCS file: /home/cvs/linux/include/asm-mips/unistd.h,v
retrieving revision 1.55
diff -u -p -r1.55 unistd.h
--- unistd.h 9 Oct 2003 15:43:22 -0000 1.55
+++ unistd.h 23 Dec 2003 17:56:25 -0000
@@ -769,17 +769,17 @@
#define __NR_statfs64 (__NR_Linux + 217)
#define __NR_fstatfs64 (__NR_Linux + 218)
#define __NR_sendfile64 (__NR_Linux + 219)
-#define __NR_timer_create (__NR_Linux + 221)
-#define __NR_timer_settime (__NR_Linux + 222)
-#define __NR_timer_gettime (__NR_Linux + 223)
-#define __NR_timer_getoverrun (__NR_Linux + 224)
-#define __NR_timer_delete (__NR_Linux + 225)
-#define __NR_clock_settime (__NR_Linux + 226)
-#define __NR_clock_gettime (__NR_Linux + 227)
-#define __NR_clock_getres (__NR_Linux + 228)
-#define __NR_clock_nanosleep (__NR_Linux + 229)
-#define __NR_tgkill (__NR_Linux + 230)
-#define __NR_utimes (__NR_Linux + 231)
+#define __NR_timer_create (__NR_Linux + 220)
+#define __NR_timer_settime (__NR_Linux + 221)
+#define __NR_timer_gettime (__NR_Linux + 222)
+#define __NR_timer_getoverrun (__NR_Linux + 223)
+#define __NR_timer_delete (__NR_Linux + 224)
+#define __NR_clock_settime (__NR_Linux + 225)
+#define __NR_clock_gettime (__NR_Linux + 226)
+#define __NR_clock_getres (__NR_Linux + 227)
+#define __NR_clock_nanosleep (__NR_Linux + 228)
+#define __NR_tgkill (__NR_Linux + 229)
+#define __NR_utimes (__NR_Linux + 230)
/*
* Offset of the last N32 flavoured syscall
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-12-23 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 17:57 Daniel Jacobowitz [this message]
2003-12-29 0:25 ` 2.5 n32 syscall numbers are wrong 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=20031223175732.GA26052@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.