From: Bernd Kuhls <bernd@kuhls.net>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH v2 1/6] build: check that outb is present in io.h
Date: Thu, 26 Oct 2023 19:14:35 +0200 [thread overview]
Message-ID: <20231026171440.4046190-2-bernd@kuhls.net> (raw)
In-Reply-To: <20231026171440.4046190-1-bernd@kuhls.net>
With glibc if io.h exists, inb/outb are always defined.
However on musl, io.h always exists but it may not define inb/outb.
Thus, igt-gpu-tools builds with musl on non-x86 platforms will fail to
link. Fix this by checking for both io.h and that outb() is defined.
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index b35a00faa..cee8a7446 100644
--- a/meson.build
+++ b/meson.build
@@ -220,7 +220,7 @@ endif
if cc.has_header('libgen.h')
config.set('HAVE_LIBGEN_H', 1)
endif
-if cc.has_header('sys/io.h')
+if cc.has_header('sys/io.h') and cc.has_function('outb', prefix: '#include <sys/io.h>')
config.set('HAVE_SYS_IO_H', 1)
endif
if cc.links('''
--
2.39.2
next prev parent reply other threads:[~2023-10-26 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 17:14 [igt-dev] [PATCH v2 0/6] Fix musl/uclibc build Bernd Kuhls
2023-10-26 17:14 ` Bernd Kuhls [this message]
2023-10-26 17:14 ` [igt-dev] [PATCH v2 2/6] Include limits.h to fix build with musl libc Bernd Kuhls
2023-10-30 14:52 ` Kamil Konieczny
2023-10-26 17:14 ` [igt-dev] [PATCH v2 3/6] lib/igt_aux.h: Fix musl build Bernd Kuhls
2023-10-26 17:14 ` [igt-dev] [PATCH v2 4/6] lib/igt_x86.c: Fix musl/uclibc build Bernd Kuhls
2023-10-26 17:14 ` [igt-dev] [PATCH v2 5/6] lib/igt_halffloat.c: " Bernd Kuhls
2023-10-26 17:14 ` [igt-dev] [PATCH v2 6/6] benchmarks/gem_exec_tracer.c: Fix musl build Bernd Kuhls
2023-10-26 19:13 ` [igt-dev] ✓ CI.xeBAT: success for Fix musl/uclibc build Patchwork
2023-10-26 19:17 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-10-28 3:33 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20231026171440.4046190-2-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=igt-dev@lists.freedesktop.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