This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] <bits/syscall.h>: Use an arch-independent system call list on Linux


* Andreas Schwab:

> On Apr 22 2017, Florian Weimer <fw@deneb.enyo.de> wrote:
>
>> I meant: If we do not rebase the UAPI headers (but backport changes as
>> needed), while still building glibc against the current upstream
>> headers (to get a complete SYS_ macro list before the backporting
>> happens).
>
> Why would you want to build a package against something that isn't part
> of the distribution?

I don't follow.  It would be an internal build dependency, like LLVM
for Mesa (in some distributions).  It would be shipped like any other
build dependency.

I have these two constraints:

a) I need to build glibc before the kernel backporting finishes.
b) I can't rebase UAPI headers to the latest upstream.

I'm under the impression you are suggesting to build glibc against a
special set of UAPI headers which aren't used by the application.
That will lead to the too aggressive SYS_ macro generation.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]