Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
media-libs/mesa-24.1.0 pulls llvm/clang
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
saski4711
Apprentice
Apprentice


Joined: 24 Jun 2004
Posts: 201

PostPosted: Thu May 23, 2024 7:45 am    Post subject: media-libs/mesa-24.1.0 pulls llvm/clang Reply with quote

Hello,

latest mesa update apparently wants to pull the whole llvm/clang chain despite USE="-llvm" is declared:

Code:

n350tw /usr/src/linux # emerge -av mesa

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 5.33 s (backtrack: 0/20).

[ebuild  N     ] sys-devel/llvm-common-18.1.6::gentoo  USE="-emacs -verify-sig" 128970 KiB
[ebuild  N     ] sys-devel/clang-common-18.1.6::gentoo  USE="cet -bootstrap-prefix -default-compiler-rt -default-libcxx -default-lld -hardened -llvm-libunwind -verify-sig" 0 KiB
[ebuild  N     ] sys-libs/binutils-libs-2.42-r1:0/2.42.0::gentoo  USE="cet nls -64-bit-bfd -multitarget -static-libs -test" ABI_X86="(64) -32 (-x32)" 26956 KiB
[ebuild  N     ] dev-util/spirv-headers-1.3.283.0::gentoo  462 KiB
[ebuild  N     ] dev-util/spirv-tools-1.3.283.0::gentoo  ABI_X86="(64) -32 (-x32)" 3104 KiB
[ebuild  N     ] sys-libs/libomp-18.1.6:0/18.1::gentoo  USE="-debug -gdb-plugin -hwloc -offload -ompt -test -verify-sig" ABI_X86="32 (64) (-x32)" LLVM_TARGETS="-AMDGPU -NVPTX" PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 KiB
[ebuild  N     ] sys-devel/llvm-18.1.6:18/18.1::gentoo  USE="binutils-plugin libffi ncurses zstd -debug -debuginfod -doc -exegesis -libedit -test -verify-sig -xml -z3" ABI_X86="(64) -32 (-x32)" LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" 265 KiB
[ebuild  N     ] sys-devel/llvmgold-18::gentoo  0 KiB
[ebuild  N     ] sys-devel/llvm-toolchain-symlinks-18:18::gentoo  USE="native-symlinks -multilib-symlinks" 0 KiB
[ebuild  N     ] sys-devel/clang-18.1.6:18/18.1::gentoo  USE="extra (pie) static-analyzer -debug -doc (-ieee-long-double) -test -verify-sig -xml" ABI_X86="(64) -32 (-x32)" LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 0 KiB
[ebuild  N     ] sys-devel/clang-toolchain-symlinks-18:18::gentoo  USE="native-symlinks -gcc-symlinks -multilib-symlinks" 0 KiB
[ebuild  N     ] sys-libs/compiler-rt-18.1.6:18::gentoo  USE="clang -debug -test -verify-sig" ABI_X86="32 (64)" 0 KiB
[ebuild  N     ] sys-libs/compiler-rt-sanitizers-18.1.6:18::gentoo  USE="asan cfi clang dfsan gwp-asan hwasan libfuzzer lsan memprof msan orc profile safestack scudo tsan ubsan xray -debug (-shadowcallstack) -test -verify-sig" ABI_X86="32 (64)" 0 KiB
[ebuild  N     ] sys-devel/clang-runtime-18.1.6:18::gentoo  USE="compiler-rt openmp sanitize -libcxx" ABI_X86="32 (64) (-x32)" 0 KiB
[ebuild  N     ] dev-python/ply-3.11-r2:0/3.11::gentoo  USE="-examples" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12 -python3_13" 160 KiB
[ebuild  N     ] sys-devel/llvm-17.0.6:17::gentoo  USE="binutils-plugin libffi ncurses zstd -debug -debuginfod -doc -exegesis -libedit -test -verify-sig -xar -xml -z3" ABI_X86="(64) -32 (-x32)" LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" 125102 KiB
[ebuild  N     ] sys-devel/llvm-toolchain-symlinks-17:17::gentoo  USE="native-symlinks -multilib-symlinks" 0 KiB
[ebuild  N     ] dev-util/spirv-llvm-translator-17.0.0-r2:17::gentoo  USE="-test" 1564 KiB
[ebuild  N     ] sys-libs/compiler-rt-17.0.6:17::gentoo  USE="clang -debug -test -verify-sig" ABI_X86="32 (64)" 0 KiB
[ebuild  N     ] sys-libs/compiler-rt-sanitizers-17.0.6:17::gentoo  USE="asan cfi clang dfsan gwp-asan hwasan libfuzzer lsan memprof msan orc profile safestack scudo tsan ubsan xray -debug (-shadowcallstack) -test -verify-sig" ABI_X86="32 (64)" 0 KiB
[ebuild  N     ] sys-devel/clang-runtime-17.0.6:17::gentoo  USE="compiler-rt openmp sanitize -libcxx" ABI_X86="32 (64) (-x32)" 0 KiB
[ebuild  N     ] sys-devel/clang-17.0.6:17::gentoo  USE="extra (pie) static-analyzer -debug -doc (-ieee-long-double) -test -verify-sig -xml" ABI_X86="(64) -32 (-x32)" LLVM_TARGETS="(AArch64) (AMDGPU) (ARM) (AVR) (BPF) (Hexagon) (Lanai) (LoongArch) (MSP430) (Mips) (NVPTX) (PowerPC) (RISCV) (Sparc) (SystemZ) (VE) (WebAssembly) (X86) (XCore) -ARC -CSKY -DirectX -M68k -SPIRV -Xtensa" PYTHON_SINGLE_TARGET="python3_11 -python3_10 -python3_12" 3 KiB
[ebuild  N     ] sys-devel/clang-toolchain-symlinks-17:17::gentoo  USE="native-symlinks -gcc-symlinks -multilib-symlinks" 0 KiB
[ebuild  N     ] dev-libs/libclc-18.1.6::gentoo  USE="spirv -verify-sig" LLVM_SLOT="17 -18" VIDEO_CARDS="-nvidia -r600 -radeonsi" 0 KiB
[ebuild  N     ] dev-util/intel_clc-24.1.0::gentoo  USE="-debug" LLVM_SLOT="17 -16" 28315 KiB
[ebuild     U  ] media-libs/mesa-24.1.0::gentoo [24.0.8::gentoo] USE="X (opengl) proprietary-codecs wayland zstd -d3d9 -debug -llvm -lm-sensors -opencl -osmesa (-selinux) -test -unwind -vaapi -valgrind -vdpau -vulkan -vulkan-overlay -xa (-zink) (-gles1%) (-gles2%*)" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2" LLVM_SLOT="17 -15 -16" VIDEO_CARDS="intel -d3d12 (-freedreno) -lavapipe (-lima) -nouveau (-nvk) (-panfrost) -r300 -r600 -radeon -radeonsi (-v3d) (-vc4) -virgl (-vivante) -vmware" 425 KiB

Total: 26 packages (1 upgrade, 25 new), Size of downloads: 315319 KiB


I'd like to keep my installation free of bloating dependencies. Is there a way to build latest mesa w/o the llvm/clang toolchain?

Regards
Saski
Back to top
View user's profile Send private message
xgivolari
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jul 2021
Posts: 102

PostPosted: Thu May 23, 2024 8:01 am    Post subject: Reply with quote

In your setup, llvm is technically not a direct dependency of mesa, but of intel_clc. In the latest mesa version, intel_clc was made a hard requirement for building mesa's intel drivers (commit).
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 22578

PostPosted: Thu May 23, 2024 12:13 pm    Post subject: Re: media-libs/mesa-24.1.0 pulls llvm/clang Reply with quote

saski4711 wrote:
I'd like to keep my installation free of bloating dependencies. Is there a way to build latest mesa w/o the llvm/clang toolchain?
I suggest you tell Portage about your requirement: use a package.mask entry to forbid Portage to install packages that you ban due to local policy. This should provoke Portage into explaining to you why it wants a masked package, at which point you can consider whether to expand the mask, change flags, or cancel the mask.
Back to top
View user's profile Send private message
saski4711
Apprentice
Apprentice


Joined: 24 Jun 2004
Posts: 201

PostPosted: Thu May 23, 2024 3:35 pm    Post subject: Re: media-libs/mesa-24.1.0 pulls llvm/clang Reply with quote

Hu wrote:
saski4711 wrote:
I'd like to keep my installation free of bloating dependencies. Is there a way to build latest mesa w/o the llvm/clang toolchain?
I suggest you tell Portage about your requirement: use a package.mask entry to forbid Portage to install packages that you ban due to local policy. This should provoke Portage into explaining to you why it wants a masked package, at which point you can consider whether to expand the mask, change flags, or cancel the mask.


No comprende on that. There are no masked packages just the requirement from dev-util/intel_clc that apparently now wants to be build with llvm/clang. And since I have an intel iGPU what good does it do to forbid portage to pull in llvm (which I did with USE="-llvm" by the way) and therefore block the update to mesa 24.1.0? Could you please explain?

In the meantime I allowed portage to pull the new dependencies resulting in a plus ~1.4GiB disk usage just to enable build for one mesa dependency. Oh what the h*ll....on the bright side my system is still smaller than a basic WIN11 installation :lol:
Back to top
View user's profile Send private message
saski4711
Apprentice
Apprentice


Joined: 24 Jun 2004
Posts: 201

PostPosted: Thu May 23, 2024 3:39 pm    Post subject: Reply with quote

xgivolari wrote:
In your setup, llvm is technically not a direct dependency of mesa, but of intel_clc. In the latest mesa version, intel_clc was made a hard requirement for building mesa's intel drivers (commit).


Thanks for the scoop. Things are getting more complex every day 8O
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 22578

PostPosted: Thu May 23, 2024 3:43 pm    Post subject: Reply with quote

In your opening post, you complained that Portage was trying to install llvm, and you did not understand why. I told you to create a package mask to tell Portage not to install llvm, so that it would be forced to explain why it wanted to do so. That would have led to an error message giving you the information that you instead had to wait for someone to provide for you. In the case that the dependency was not mandatory for your setup, it would have let you find how to disable it, and would continue to keep llvm off your system in the future.
Back to top
View user's profile Send private message
saski4711
Apprentice
Apprentice


Joined: 24 Jun 2004
Posts: 201

PostPosted: Thu May 23, 2024 4:07 pm    Post subject: Reply with quote

Hu wrote:
In your opening post, you complained that Portage was trying to install llvm, and you did not understand why. I told you to create a package mask to tell Portage not to install llvm, so that it would be forced to explain why it wanted to do so. That would have led to an error message giving you the information that you instead had to wait for someone to provide for you. In the case that the dependency was not mandatory for your setup, it would have let you find how to disable it, and would continue to keep llvm off your system in the future.


Ah okay now I understand. Will try that on my laptop after syncing the portage tree. Tkanks for the advice :).
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum