This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/24532] New: conform/arpa/inet.h failures due to linux kernel 64-bit time_t changes
- From: "wilson at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 07 May 2019 21:43:23 +0000
- Subject: [Bug libc/24532] New: conform/arpa/inet.h failures due to linux kernel 64-bit time_t changes
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=24532
Bug ID: 24532
Summary: conform/arpa/inet.h failures due to linux kernel
64-bit time_t changes
Product: glibc
Version: 2.30
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: wilson at gcc dot gnu.org
CC: drepper.fsp at gmail dot com
Target Milestone: ---
As part of the 64-bit time_t y2038 changes, the linux kernel modified
asm-generic/socket.h to include linux/posix_types.h.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/asm-generic/socket.h?h=v5.1&id=a623a7a1a5670c25a16881f5078072d272d96b71
Unfortunately, linux/posix_types.h defines a structure with a field called
fds_bits. It also includes asm-generic/posix_types.h which defines a structure
with a field called val. The existence of these two structure fields is
causing me to see conform failures.
In the make check output I see
FAIL: conform/POSIX2008/arpa/inet.h/conform
FAIL: conform/POSIX2008/netdb.h/conform
FAIL: conform/POSIX2008/netinet/in.h/conform
FAIL: conform/POSIX2008/sys/socket.h/conform
which then repeats for four other standard versions for a total of 20 failures.
In conform/POSIX2008/arpa/inet.h/conform.out I see
Namespace violation: "fds_bits"
Namespace violation: "val"
FAIL: Namespace of <arpa/inet.h>
and similarly for the other header files.
I'm seeing these failures on a RISC-V Fedora Core 30 system, with 5.1.0 linux
kernel headers, building top of tree glibc sources, and running make check.
Maybe this is actually a linux kernel bug, but it is glibc make check that is
broken, so I thought I would start here. I don't know how these linux/glibc
interaction problems are dealt with normally.
--
You are receiving this mail because:
You are on the CC list for the bug.