From: Jack <ostroffjh@users.sourceforge.net>
To: Gentoo User List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Upgrade problems with the latest llvm/clang
Date: Tue, 23 Jul 2024 17:37:19 -0400 [thread overview]
Message-ID: <IGTBLIVE.NIT6V46F.ENYUZB4V@6HBPP7FK.AFFBPYFL.V2UJ26EV> (raw)
The latest eix-sync included clang and llvm 18. Unfortunately, a full
emerge upgrade complains
- media-libs/mesa-24.1.3::gentoo USE="X llvm lm-sensors (opengl)
proprietary-codecs vaapi vulkan wayland zstd -d3d9 -debug -opencl
-osmesa (-selinux) -test -unwind -valgrind -vdpau -vulkan-overlay -xa"
ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="-15 -16 -17
(-18)" VIDEO_CARDS="radeon radeonsi -d3d12 (-freedreno) -intel
-lavapipe (-lima) -nouveau (-nvk) (-panfrost) -r300 -r600 (-v3d) (-vc4)
-virgl (-vivante) -vmware -zink"
The following REQUIRED_USE flag constraints are unsatisfied:
llvm? ( exactly-one-of ( llvm_slot_15 llvm_slot_16 llvm_slot_17
llvm_slot_18 ) )
The problem is that I don't know why one of the llvm slots is NOT
selected.
"emerge --info mesa" includes:
USE="X llvm lm-sensors (opengl) proprietary-codecs vaapi vulkan wayland
zstd -d3d9 -debug -opencl -osmesa (-selinux) -test -unwind -valgrind
-vdpau -vulkan-overlay -xa" ABI_X86="32 (64) (-x32)"
CPU_FLAGS_X86="sse2" LLVM_SLOT="17 -15 -16 (-18)" VIDEO_CARDS="radeon
radeonsi -d3d12 (-freedreno) -intel -lavapipe (-lima) -nouveau (-nvk)
(-panfrost) -r300 -r600 (-v3d) (-vc4) -virgl (-vivante) -vmware -zink"
which shows slot 17 IS selected.
"grep -ir llvm /etc/portage" only shows sys-devel/llvm abi_x86_32 in
one of the package.use files.
My profile is
default/linux/amd64/23.0/desktop/plasma (stable) *
I find no relevant bug filed, and nothing related on the forums. What
fine manual have I apparently neglected to read?
Jack
next reply other threads:[~2024-07-23 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 21:37 Jack [this message]
2024-07-23 21:52 ` [gentoo-user] Upgrade problems with the latest llvm/clang Eli Schwartz
2024-07-24 17:57 ` Jack
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=IGTBLIVE.NIT6V46F.ENYUZB4V@6HBPP7FK.AFFBPYFL.V2UJ26EV \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.gentoo.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