Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH 1/7] build: check that outb is present in io.h
Date: Sun, 22 Oct 2023 17:52:20 +0200	[thread overview]
Message-ID: <20231022155226.3484622-2-bernd@kuhls.net> (raw)
In-Reply-To: <20231022155226.3484622-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

  reply	other threads:[~2023-10-22 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 15:52 [igt-dev] [PATCH 0/7] igt: Fix musl build Bernd Kuhls
2023-10-22 15:52 ` Bernd Kuhls [this message]
2023-10-22 15:52 ` [igt-dev] [PATCH 2/7] Include limits.h to fix build with musl libc Bernd Kuhls
2023-10-24 15:59   ` Kamil Konieczny
2023-10-22 15:52 ` [igt-dev] [PATCH 3/7] lib/igt_aux.h: Fix musl build Bernd Kuhls
2023-10-24 16:16   ` Kamil Konieczny
2023-10-22 15:52 ` [igt-dev] [PATCH 4/7] lib/igt_x86.c: Fix musl/uclibc build Bernd Kuhls
2023-10-22 15:52 ` [igt-dev] [PATCH 5/7] lib/igt_halffloat.c: " Bernd Kuhls
2023-10-22 15:52 ` [igt-dev] [PATCH 6/7] benchmarks/gem_exec_tracer.c: Fix musl build Bernd Kuhls
2023-10-24 16:09   ` Kamil Konieczny
2023-10-22 15:52 ` [igt-dev] [PATCH 7/7] benchmarks/gem_syslatency.c: " Bernd Kuhls

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=20231022155226.3484622-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