From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] <bits/syscall.h>: Use an arch-independent system call list on Linux
Date: Thu, 06 Apr 2017 10:12:00 -0000 [thread overview]
Message-ID: <0be44a08-16c1-e904-272a-6322f51e7b0c@redhat.com> (raw)
In-Reply-To: <mvminmhetn1.fsf@suse.de>
On 04/06/2017 12:07 PM, Andreas Schwab wrote:
> On Apr 06 2017, Florian Weimer <fweimer@redhat.com> wrote:
>
>> I think the argument was that __NR_* should come from the kernel, and
>> SYS_* should come from glibc, and that the kernel has no business defining
>> SYS_* macros, purely based on namespace concerns.
>
> I don't know why you are talking about SYS_. All that the kernel
> defines are __NR_. The SYS_ defines are pure glibc stuff.
The separation is what causes problems because there is no way to tell
the C preprocessor to export all __NR_* macros as SYS_* macros, too.
As a result, current glibc has this elaborate dance at built where it
runs “gcc -E -dM” (with varying additional parameters to get the
lib/libx32/lib64 variants). I want to get rid of that because it means
that if you upgrade the kernel headers after building glibc, the SYS_*
and __NR_* macros drift apart.
>> Not sure if we are talking about the same thing. Our kernel-headers
>> package comes from the kernel sources, 3.10 era.
>
> Consider splitting it out, they are really independent. Then you can
> update the kernel headers without touching the kernel.
But I'd still have the issue that the kernel headers contain only the
__NR_* macros, not the SYS_* macros.
If you think that SYS_* macros should remain glibc business, then I
think the patch I posted is the right approach to simplify independent
kernel header updates (whether they come from a separate package, or
directly from the upstream sources).
Thanks,
Florian
next prev parent reply other threads:[~2017-04-06 10:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 19:40 Florian Weimer
2017-04-06 8:00 ` Andreas Schwab
2017-04-06 8:52 ` Florian Weimer
2017-04-06 9:03 ` Andreas Schwab
2017-04-06 9:47 ` Florian Weimer
2017-04-06 10:07 ` Andreas Schwab
2017-04-06 10:12 ` Florian Weimer [this message]
2017-04-06 12:29 ` Andreas Schwab
2017-04-06 12:32 ` Florian Weimer
2017-04-06 12:49 ` Andreas Schwab
2017-04-06 13:24 ` Florian Weimer
2017-04-06 13:44 ` Andreas Schwab
2017-04-06 14:22 ` Florian Weimer
2017-04-06 14:37 ` Dmitry V. Levin
2017-04-21 10:06 ` Florian Weimer
2017-04-21 12:27 ` Andreas Schwab
2017-04-21 12:37 ` Florian Weimer
2017-04-21 18:31 ` Carlos O'Donell
2017-04-21 18:02 ` Andreas Schwab
2017-04-21 18:46 ` Florian Weimer
2017-04-21 19:08 ` Andreas Schwab
2017-04-21 19:15 ` Florian Weimer
2017-04-21 19:34 ` Andreas Schwab
2017-04-21 19:37 ` Florian Weimer
2017-04-21 19:40 ` Andreas Schwab
2017-04-21 19:57 ` Florian Weimer
2017-04-22 9:38 ` Andreas Schwab
2017-04-22 11:59 ` Florian Weimer
2017-04-22 13:45 ` Andreas Schwab
2017-04-22 14:22 ` Florian Weimer
2017-04-22 15:08 ` Andreas Schwab
2017-04-22 15:27 ` Florian Weimer
2017-04-22 15:37 ` Andreas Schwab
2017-04-22 15:51 ` Florian Weimer
2017-04-22 17:27 ` Andreas Schwab
2017-08-24 14:35 ` Carlos O'Donell
2017-08-24 15:15 ` Joseph Myers
2017-08-24 16:08 ` Carlos O'Donell
2017-08-24 18:49 ` Florian Weimer
2017-08-24 20:28 ` Joseph Myers
2017-08-25 14:30 ` Florian Weimer
2017-08-25 15:40 ` Joseph Myers
2017-08-25 15:57 ` Florian Weimer
2017-08-28 11:36 ` Joseph Myers
2017-08-28 12:35 ` Florian Weimer
2017-08-28 12:43 ` Joseph Myers
2017-04-23 0:35 ` synchronizing kernel UAPI and libc headers Dmitry V. Levin
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=0be44a08-16c1-e904-272a-6322f51e7b0c@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).