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 are compatible with other non-Linux systems, and also because they are the documented way for user space. However, there was some concern that someone might be running a new kernel with an old glibc, and that __NR_xxx symbols might be available but not SYS_xxx in that case. Since the <bits/syscall.h> (included through <sys/syscall.h>) header is generated automatically from the kernel headers at glibc build time, Debian should make sure that the latest available kernel headers are used, so building the latest Sid glibc package should be done on a system with also the latest kernel available in Sid, to have a complete SYS_xxx list. Cheers, Alex -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6-dev depends on: ii libc-dev-bin 2.33-8 ii libc6 2.33-8 ii libcrypt-dev 1:4.4.28-2 ii libnsl-dev 1.3.0-2 ii linux-libc-dev 5.18.5-1 ii rpcsvc-proto 1.4.2-4 libc6-dev recommends no packages. Versions of packages libc6-dev suggests: pn glibc-doc <none> ii manpages-dev 5.13-1 -- no debconf information