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 0/7] igt: Fix musl build
Date: Sun, 22 Oct 2023 17:52:19 +0200	[thread overview]
Message-ID: <20231022155226.3484622-1-bernd@kuhls.net> (raw)

Hi,

this is my first patch series I am sending so please be patient ;)

Currently there are efforts underway to add a igt-gpu-tools package to
the buildroot project. Besides glibc buildroot also supports musl- and
uClibc-based toolchains. While testing the new package it turns out that
igt-gpu-tools does not build with other libc's out of the box, see
https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/138

This patch series tries to solve the request from the bug tracker that
the void-linux patch is "splitted into some functional changes".

During build I added only those parts of the void-linux patch which were
needed to fix build errors, I quoted those errors in each patch message.
Besides that, due to my non-knowledge of C, I can not provide any more
information.

Regards, Bernd


Bernd Kuhls (1):
  build: check that outb is present in io.h

Stefano Ragni (5):
  Include limits.h to fix build with musl libc
  lib/igt_aux.h: Fix musl build
  lib/igt_x86.c: Fix musl/uclibc build
  lib/igt_halffloat.c: Fix musl/uclibc build
  benchmarks/gem_syslatency.c: Fix musl build

mhmdanas (1):
  benchmarks/gem_exec_tracer.c: Fix musl build

 benchmarks/gem_exec_tracer.c  | 4 ++++
 benchmarks/gem_syslatency.c   | 2 ++
 lib/amdgpu/amd_pci_unplug.c   | 1 +
 lib/igt_audio.c               | 1 +
 lib/igt_aux.c                 | 1 +
 lib/igt_aux.h                 | 2 +-
 lib/igt_device_scan.c         | 1 +
 lib/igt_eld.c                 | 1 +
 lib/igt_frame.c               | 1 +
 lib/igt_halffloat.c           | 2 +-
 lib/igt_hwmon.c               | 1 +
 lib/igt_x86.c                 | 2 +-
 meson.build                   | 2 +-
 runner/executor.c             | 1 +
 runner/runner_tests.c         | 1 +
 tests/device_reset.c          | 1 +
 tests/intel/i915_pm_rpm.c     | 1 +
 tests/kms_sysfs_edid_timing.c | 1 +
 tests/testdisplay.c           | 1 +
 tests/tools_test.c            | 1 +
 tools/igt_compliance_utils.c  | 1 +
 21 files changed, 25 insertions(+), 4 deletions(-)

-- 
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 Bernd Kuhls [this message]
2023-10-22 15:52 ` [igt-dev] [PATCH 1/7] build: check that outb is present in io.h Bernd Kuhls
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-1-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