From: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org
Subject: Re: [PATCH roland/getrlimit] Re: Bug 14138 - Move some functions to syscalls.list
Date: Mon, 20 Aug 2012 13:14:00 -0000 [thread overview]
Message-ID: <50323809.7090309@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120726185950.D07662C064@topped-with-meat.com>
On 26/07/12 20:59, Roland McGrath wrote:
>> Adding this line to linux/syscalls.list:
>>
>> getrlimit - ugetrlimit i:ip __new_getrlimit __getrlimit getrlimit@@GLIBC_2.2
>>
>> The unix/syscalls.list takes precendence of the linux one. So, this did
>> not work out for x86 ;( Or did I made an error?
>
> What exactly does that mean? What getrlimit-related lines appear in the
> sysd-syscalls generated after the change?
>
>> Btw. I removed the linux/i386/getrlimit.c file for this as well,
>
> Yes, that's necessary.
>
> Anyway, you must have made some error, because it worked for me.
> The change below is on the roland/getrlimit branch.
>
> It needs testing and sign-off from powerpc, sh, am33, arm, and m68k
> maintainers.
>
>
> Thanks,
> Roland
>
>
> 2012-07-26 Roland McGrath <roland@hack.frob.com>
>
> [BZ #14138]
> * sysdeps/unix/sysv/linux/syscalls.list: Add getrlimit/ugetrlimit line.
> * sysdeps/unix/sysv/linux/i386/getrlimit.c: File removed.
> * sysdeps/unix/sysv/linux/powerpc/getrlimit.c: File removed.
> * sysdeps/unix/sysv/linux/sh/getrlimit.c: File removed.
>
> ports/ChangeLog.am33
> 2012-07-26 Roland McGrath <roland@hack.frob.com>
>
> [BZ #14138]
> * sysdeps/unix/sysv/linux/am33/getrlimit.c: File removed.
>
> ports/ChangeLog.arm
> 2012-07-26 Roland McGrath <roland@hack.frob.com>
>
> [BZ #14138]
> * sysdeps/unix/sysv/linux/arm/getrlimit.c: File removed.
>
> ports/ChangeLog.m68k
> 2012-07-26 Roland McGrath <roland@hack.frob.com>
>
> [BZ #14138]
> * sysdeps/unix/sysv/linux/m68k/getrlimit.c: File removed.
sysdeps/unix/sysv/linux/s390/s390-32/getrlimit.c should be removed as well. Done with the
patch I've just comitted:
2012-08-20 Andreas Krebbel <Andreas.Krebbel@de.ibm.com>
* sysdeps/unix/sysv/linux/s390/s390-32/getrlimit.c: Remove.
---
sysdeps/unix/sysv/linux/s390/s390-32/getrlimit.c | 1 -
1 file changed, 1 deletion(-)
Index: glibc/sysdeps/unix/sysv/linux/s390/s390-32/getrlimit.c
===================================================================
--- glibc.orig/sysdeps/unix/sysv/linux/s390/s390-32/getrlimit.c
+++ /dev/null
@@ -1 +0,0 @@
-#include <sysdeps/unix/sysv/linux/i386/getrlimit.c>
prev parent reply other threads:[~2012-08-20 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50103612.3050308@suse.com>
[not found] ` <20120725203222.AF6452C0E2@topped-with-meat.com>
[not found] ` <5296462.88fGOZ3lSr@byrd>
2012-07-26 19:00 ` Roland McGrath
2012-07-26 19:37 ` Andreas Jaeger
2012-07-26 19:59 ` Andreas Schwab
2012-07-26 20:24 ` Joseph S. Myers
2012-07-26 20:48 ` Roland McGrath
2012-07-26 22:06 ` Roland McGrath
2012-07-27 14:18 ` Joseph S. Myers
2012-07-27 16:16 ` Roland McGrath
2012-07-27 18:39 ` Joseph S. Myers
2012-07-27 20:12 ` Roland McGrath
2012-08-01 17:19 ` Ryan S. Arnold
2012-08-01 17:26 ` Roland McGrath
2012-07-27 23:28 ` Kaz Kojima
2012-08-01 18:47 ` Mark Salter
2012-08-20 13:14 ` Andreas Krebbel [this message]
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=50323809.7090309@linux.vnet.ibm.com \
--to=krebbel@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.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).