From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix fcntl on s390x and other arches
Date: Sun, 07 Sep 2003 11:58:00 -0000 [thread overview]
Message-ID: <20030907095715.GE12344@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <u8wucny2gk.fsf@gromit.moeb>
Hi!
On Fri, Sep 05, 2003 at 12:06:03PM +0200, Andreas Jaeger wrote:
> Ulrich Drepper <drepper@redhat.com> writes:
>
> > Andreas Jaeger wrote:
> >
> >> Ok to commit?
> >
> > Yes.
>
> Ok, now both x86-64 and i386 work (with linuxthreads and tls) again
> (with two further obvious and committed fcntl change) for me,
That way we'd have to update all arches not having their own fcntl.c
(e.g. s390x fails to build in current CVS).
This is IMHO better:
2003-09-07 Jakub Jelinek <jakub@redhat.com>
* sysdeps/unix/sysv/linux/syscalls.list (fcntl): Remove.
* sysdeps/unix/sysv/linux/x86_64/fcntl.c: Remove.
--- libc/sysdeps/unix/sysv/linux/syscalls.list.jj 2003-08-26 17:07:48.000000000 -0400
+++ libc/sysdeps/unix/sysv/linux/syscalls.list 2003-09-07 06:59:15.000000000 -0400
@@ -73,7 +73,6 @@ uselib EXTRA uselib i:s uselib
wait4 - wait4 i:iWiP __wait4 wait4
chown - chown i:sii __libc_chown __chown chown
-fcntl - fcntl Ci:iiF __libc_fcntl __fcntl fcntl
setxattr - setxattr i:sspii setxattr
lsetxattr - lsetxattr i:sspii lsetxattr
--- libc/sysdeps/unix/sysv/linux/x86_64/fcntl.c.jj 2003-09-05 04:44:35.000000000 -0400
+++ libc/sysdeps/unix/sysv/linux/x86_64/fcntl.c 2003-09-07 06:59:01.000000000 -0400
@@ -1 +0,0 @@
-#include <sysdeps/unix/sysv/linux/fcntl.c>
Jakub
next prev parent reply other threads:[~2003-09-07 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 5:13 Fix i386/fcntl.c Andreas Jaeger
2003-09-05 5:33 ` Ulrich Drepper
2003-09-05 10:06 ` Andreas Jaeger
2003-09-07 11:58 ` Jakub Jelinek [this message]
2003-09-07 12:07 ` [PATCH] Fix fcntl on s390x and other arches Andreas Jaeger
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=20030907095715.GE12344@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=aj@suse.de \
--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).