From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15916] mesa3d fails to build
Date: Tue, 19 Mar 2024 07:55:04 +0000 [thread overview]
Message-ID: <bug-15916-163-bO1YqSrRSH@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15916-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15916
--- Comment #1 from Dr I J Ormshaw <ian_ormshaw@waters.com> ---
Adding spirv tools on my build system
$ dnf5 list --installed *spirv*
Installed packages
spirv-headers-devel.noarch 1.5.5-20.fc39 updates
spirv-llvm-translator.x86_64 17.0.0-1.fc39 fedora
spirv-tools.x86_64 2023.3-3.fc39 updates
spirv-tools-devel.x86_64 2023.3-3.fc39 updates
spirv-tools-libs.x86_64 2023.3-3.fc39 updates
And setting
Symbol: BR2_PACKAGE_SPIRV_HEADERS [=y]
Symbol: BR2_PACKAGE_SPIRV_TOOLS [=y]
gives the followinf error:
Found CMake: /usr/bin/cmake (3.27.7)
Run-time dependency spirv-tools found: NO (tried pkgconfig and cmake)
../../../../../build/x86_64-WatersAMST-linux-gnu_24-support-mesa3d-gallium-amdgpu-opencl-e791e9b4/build/mesa3d-24.0.0/meson.build:1843:20:
ERROR: Dependency "SPIRV-Tools" not found, tried pkgconfig and cmake
A full log can be found at
/home/ian/build/x86_64-WatersAMST-linux-gnu_24-support-mesa3d-gallium-amdgpu-opencl-e791e9b4/build/mesa3d-24.0.0/build/meson-logs/meson-log.txt
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-19 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:09 [Buildroot] [Bug 15916] New: mesa3d fails to build bugzilla
2024-03-19 7:55 ` bugzilla [this message]
2024-03-19 8:03 ` [Buildroot] [Bug 15916] " bugzilla
2024-06-15 15:24 ` bugzilla
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=bug-15916-163-bO1YqSrRSH@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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