From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@redhat.com>, Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix sparc64 build
Date: Sun, 29 Sep 2002 13:28:00 -0000 [thread overview]
Message-ID: <20020929222809.K3451@sunsite.ms.mff.cuni.cz> (raw)
Hi!
Without this I got
../sysdeps/unix/sysv/linux/seteuid.c:26:58: operator '>' has no left operand
error in sparc64 build.
Verified no other broken defines like this are in kernel-features.h.
sparc32 make check is still ongoing, so far only bug-regex12 failed.
Also, one note to all the builds - they were done with the __ctype_b etc.
exporting patch as @@GLIBC*, not @GLIBC*, so although it works for me on
ia64, it probably doesn't work for others there due to ld issues.
2002-09-29 Jakub Jelinek <jakub@redhat.com>
* sysdeps/unix/sysv/linux/kernel-features.h
(__ASSUME_SETRESUID_SYSCALL): On the sparc, define to 1, not empty.
--- libc/sysdeps/unix/sysv/linux/kernel-features.h.jj 2002-09-18 00:31:46.000000000 +0200
+++ libc/sysdeps/unix/sysv/linux/kernel-features.h 2002-09-29 22:28:04.000000000 +0200
@@ -124,7 +124,7 @@
/* Linux 2.3.39 sparc added setresuid. */
#if __LINUX_KERNEL_VERSION >= 131879 && defined __sparc__
-# define __ASSUME_SETRESUID_SYSCALL
+# define __ASSUME_SETRESUID_SYSCALL 1
#endif
/* Linux 2.3.39 introduced IPC64. Except for powerpc. */
Jakub
next reply other threads:[~2002-09-29 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 13:28 Jakub Jelinek [this message]
2002-09-29 13:42 ` Ulrich Drepper
2003-04-14 13:36 Jakub Jelinek
2003-04-14 16:49 ` Ulrich Drepper
2006-01-31 21:59 Jakub Jelinek
2006-03-01 21:19 Jakub Jelinek
2006-08-10 6:53 Jakub Jelinek
2006-08-10 20:56 ` Roland McGrath
2006-08-15 5:28 ` Ulrich Drepper
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=20020929222809.K3451@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).