Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-25 Thread Alejandro Colomar
Hi Aurelien, On 7/25/22 19:39, Aurelien Jarno wrote: On 2022-07-25 14:51, Alejandro Colomar wrote: E.g., when one runs `apt-get upgrade`, if the kernel is upgraded, update-libc-syscalls(1) would be called by apt-get as a post install script, and libc macros would have the new syscall numbers pr

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-25 Thread Aurelien Jarno
On 2022-07-25 14:51, Alejandro Colomar wrote: > Hi Florian! > > On 7/25/22 12:38, Florian Weimer wrote: > > * Alejandro Colomar via Libc-alpha: > > > > > Is there an easy way to regenerate that header to get the tatest > > > syscalls? Maybe a command could be supplied so that users (or at > > >

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-25 Thread Florian Weimer
* Alejandro Colomar: > Hi Florian! > > On 7/25/22 12:38, Florian Weimer wrote: >> * Alejandro Colomar via Libc-alpha: >> >>> Is there an easy way to regenerate that header to get the tatest >>> syscalls? Maybe a command could be supplied so that users (or at >>> least distributors) have it easy

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-25 Thread Alejandro Colomar
Hi Florian! On 7/25/22 12:38, Florian Weimer wrote: * Alejandro Colomar via Libc-alpha: Is there an easy way to regenerate that header to get the tatest syscalls? Maybe a command could be supplied so that users (or at least distributors) have it easy to regenerate them? Maybe it already exis

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-25 Thread Florian Weimer
* Alejandro Colomar via Libc-alpha: > Is there an easy way to regenerate that header to get the tatest > syscalls? Maybe a command could be supplied so that users (or at > least distributors) have it easy to regenerate them? Maybe it already > exists but it's not widely known? I have recently b

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-24 Thread Alejandro Colomar (man-pages)
[CC += libc-alpha] Hi glibc developers, On 7/24/22 14:24, Aurelien Jarno wrote: Hi, On 2022-07-24 12:39, Alejandro Colomar (man-pages) wrote: Hi Aurelien, On 7/23/22 11:43, Aurelien Jarno wrote: Hi, On 2022-07-19 21:55, Alejandro Colomar wrote: Package: libc6-dev Version: 2.33-8 Severity:

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-24 Thread Aurelien Jarno
Hi, On 2022-07-24 12:39, Alejandro Colomar (man-pages) wrote: > Hi Aurelien, > > On 7/23/22 11:43, Aurelien Jarno wrote: > > Hi, > > > > On 2022-07-19 21:55, Alejandro Colomar wrote: > > > Package: libc6-dev > > > Version: 2.33-8 > > > Severity: normal > > > X-Debbugs-Cc: alx.manpa...@gmail.com

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-24 Thread Alejandro Colomar (man-pages)
Hi Aurelien, On 7/23/22 11:43, Aurelien Jarno wrote: Hi, On 2022-07-19 21:55, Alejandro Colomar wrote: Package: libc6-dev Version: 2.33-8 Severity: normal X-Debbugs-Cc: alx.manpa...@gmail.com Hi, We had a discussion in NGINX Unit about if we should use __NR_xxx or SYS_xxx syscall numbers.

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-23 Thread Aurelien Jarno
Hi, On 2022-07-19 21:55, Alejandro Colomar wrote: > Package: libc6-dev > Version: 2.33-8 > Severity: normal > X-Debbugs-Cc: alx.manpa...@gmail.com > > > Hi, > > We had a discussion in NGINX Unit about if we should use __NR_xxx > or SYS_xxx syscall numbers. As maintainer of the Linux man-pages,

Bug#1015719: libc6-dev: Build glibc with latest packaged kernel version

2022-07-19 Thread Alejandro Colomar
Package: libc6-dev Version: 2.33-8 Severity: normal X-Debbugs-Cc: alx.manpa...@gmail.com Hi, We had a discussion in NGINX Unit about if we should use __NR_xxx or SYS_xxx syscall numbers. As maintainer of the Linux man-pages, I suggested that we should use the libc macros (SYS_xxx), since they a