From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Andrzej Hajda <andrzej.hajda@intel.com>
Subject: [PATCH i-g-t 0/1] Fix dist building with iga64 codes script
Date: Thu, 12 Dec 2024 11:52:30 +0100 [thread overview]
Message-ID: <20241212105231.49481-1-kamil.konieczny@linux.intel.com> (raw)
Currently distro building with meson is failing:
mkdir build
meson setup build
ninja -C build dist
with:
[300/1928] Generating lib/iga64_generated_codes.c with a custom command
FAILED: lib/iga64_generated_codes.c
build/meson-private/dist-unpack/igt-gpu-tools-1.29/scripts/generate_iga64_codes: line 43: ../lib/iga64_macros.h: No such file or directory
Generating new lib/iga64_generated_codes.c
Generating iga64_code_gpgpu_fill for platform 2
<command-line>: fatal error: ../lib/iga64_macros.h: No such file or directory
compilation terminated.
DIE: cpp error for iga64_assembly_gpgpu_fill.2
Fix the script to find correct path and also bail out gracefully
when it will not be find.
Cc: Andrzej Hajda <andrzej.hajda@intel.com>
Kamil Konieczny (1):
scripts/generate_iga64_codes: Fix dist build
scripts/generate_iga64_codes | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
--
2.47.1
next reply other threads:[~2024-12-12 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 10:52 Kamil Konieczny [this message]
2024-12-12 10:52 ` [PATCH i-g-t 1/1] scripts/generate_iga64_codes: Fix dist build Kamil Konieczny
2024-12-12 12:15 ` ✓ Xe.CI.BAT: success for Fix dist building with iga64 codes script Patchwork
2024-12-12 12:33 ` ✓ i915.CI.BAT: " Patchwork
2024-12-12 17:18 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-12 19:19 ` Kamil Konieczny
2024-12-12 18:13 ` ✗ Xe.CI.Full: " Patchwork
2024-12-12 19:17 ` Kamil Konieczny
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=20241212105231.49481-1-kamil.konieczny@linux.intel.com \
--to=kamil.konieczny@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--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