From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: util-linux <util-linux@vger.kernel.org>
Cc: Michael Cree <mcree@orcon.net.nz>, Sam James <sam@gentoo.org>
Subject: util-linux fails to build on alpha due to test_enosys
Date: Fri, 01 Dec 2023 09:17:20 +0100 [thread overview]
Message-ID: <9211accf8670f28778166a1acdc186e8dd28f2e8.camel@physik.fu-berlin.de> (raw)
Hello!
Since version 2.39.2, util-linux fails to build from source since tests/helpers/test_enosys.c
is built even though alpha is not supported by libseccomp and does not have AUDIT_ARCH_NATIVE:
gcc -DHAVE_CONFIG_H -I. -include config.h -I./include -DLOCALEDIR=\"/usr/share/locale\" -D_PATH_RUNSTATEDIR=\"/run\" -D_PATH_SYSCONFSTATICDIR=\"/usr/lib\" -Wdate-time -D_FORTIFY_SOURCE=2 -fsigned-
char -fno-common -Wall -Wextra -Waddress-of-packed-member -Wdiscarded-qualifiers -Wimplicit-function-declaration -Wmissing-declarations -Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs -
Wno-missing-field-initializers -Wold-style-definition -Wpointer-arith -Wredundant-decls -Wsign-compare -Wstrict-prototypes -Wtype-limits -Wuninitialized -Wunused-but-set-parameter -Wunused-but-set-
variable -Wunused-parameter -Wunused-result -Wunused-variable -Werror=sequence-point -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -Wformat -Werror=format-security -c -o tests/helpers/test_enosys.o
tests/helpers/test_enosys.c
In file included from tests/helpers/test_enosys.c:30:
./include/audit-arch.h:67:6: error: #error Unknown target architecture
67 | # error Unknown target architecture
| ^~~~~
Full log available in [1].
Sam James from Gentoo suggested this might due to test_enosys being built unconditionally [2]
while enosys requires AUDIT_ARCH_NATIVE [3]. On the other hand, we're not seeing this issue
on sparc64 which currently doesn't have libseccomp support either.
Any suggestions?
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=util-linux&arch=alpha&ver=2.39.2-1&stamp=1692576237&raw=0
> [2] https://github.com/util-linux/util-linux/blob/master/meson.build#L3414
> [3] https://github.com/util-linux/util-linux/blob/master/meson.build#L2947
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next reply other threads:[~2023-12-01 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 8:17 John Paul Adrian Glaubitz [this message]
2023-12-01 8:50 ` util-linux fails to build on alpha due to test_enosys Thomas Weißschuh
2023-12-01 8:58 ` John Paul Adrian Glaubitz
2023-12-01 13:55 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9211accf8670f28778166a1acdc186e8dd28f2e8.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=mcree@orcon.net.nz \
--cc=sam@gentoo.org \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).