On Mon, Jun 27, 2022 at 9:47 AM <soe...@soeren-tempel.net> wrote:
>
> From: Sören Tempel <soe...@soeren-tempel.net>
>
> This patch addresses two minor compatibility issues with musl libc:
>
> * On some architecture (e.g. PowerPC), musl has more than one field
> prefixed with st_{a,m,c}tim in struct stat. This causes the sed(1)
> invocation to not work correctly (since it will only replace the first
> occurrence) [1]. This can be fixed by passing the 'g' flag to replace
> all occurrences.
> * Since version 1.2.3, musl defines SYS_SECCOMP in signal.h [2]. This
> conflicts with mksysinfo extraction of syscall numbers [3]. By
> restricting the grep expression to only match lower case characters we
> can avoid a redefinition of SYS_SECCOMP. This is GCC PR 105225.
>
> This patch combines two Alpine Linux patches which have been written by
> Ariadne Conill and Natanael Copa. I haven't tested this with glibc but I
> strongly suspect that both changes should not introduce any issue with
> glibc.
Given that pretty much every one of these musl patches has led to
problems on some glibc systems, it would be very nice if you could do
some testing with glibc. Thanks.
Can you expand on the st_atim issue? What does the musl type look
like in gen-sysinfo.go?
What is the value of SYS_SECCOMP in musl? Is it a system call number?
What does it look like in gen-sysinfo.go?
Thanks.
Ian
