lib32-llvm
and lib32-llvm-libs
is updated again.
both are currently version 1:19.1.7-1
https://archlinux.org/packages/multilib/x86_64/lib32-llvm/
https://archlinux.org/packages/multilib/x86_64/lib32-llvm-libs/
Git Clone URL: | https://aur.archlinux.org/lib32-mesa-git.git (read-only, click to copy) |
---|---|
Package Base: | lib32-mesa-git |
Description: | an open-source implementation of the OpenGL specification, git version |
Upstream URL: | https://www.mesa3d.org |
Licenses: | custom |
Conflicts: | lib32-libva-mesa-driver, lib32-mesa, lib32-mesa-libgl, lib32-mesa-vdpau, lib32-vulkan-intel, lib32-vulkan-mesa-layers, lib32-vulkan-radeon |
Provides: | lib32-libva-mesa-driver, lib32-mesa, lib32-mesa-libgl, lib32-mesa-vdpau, lib32-opengl-driver, lib32-vulkan-driver, lib32-vulkan-intel, lib32-vulkan-mesa-layers, lib32-vulkan-radeon |
Submitter: | None |
Maintainer: | rjahanbakhshi (Lone_Wolf) |
Last Packager: | rjahanbakhshi |
Votes: | 44 |
Popularity: | 0.009854 |
First Submitted: | 2009-12-18 18:42 (UTC) |
Last Updated: | 2025-01-13 05:52 (UTC) |
lib32-llvm
and lib32-llvm-libs
is updated again.
both are currently version 1:19.1.7-1
https://archlinux.org/packages/multilib/x86_64/lib32-llvm/
https://archlinux.org/packages/multilib/x86_64/lib32-llvm-libs/
won't build because of a bunch of LLVM_MAKE related errors
/usr/include/clang/Driver/Options.inc:65:275: error: macro "LLVM_MAKE_OPT_ID" passed 14 arguments, but takes just 13
65 | OPTION(llvm::ArrayRef<llvm::StringLiteral>(), "<action group>", Action_Group, Group, INVALID, INVALID, nullptr, 0, 0, 0, nullptr, (std::array<std::pair<std::array<unsigned, 2>, const char*>, 1>{{ std::make_pair(std::array<unsigned, 2>{{0, 0}}, nullptr) }}), nullptr, nullptr)
| ^
lib32-llvm
and lib32-llvm-libs
has been updated to 1:19.1.6-3
in stable repo.
And the PKGBUILD require update to build.
Also latest SVGA
MR broke x86_32 compilation issue #12451
lib32-llvm
and lib32-llvm-libs
package in stable repo has been "updated" to 1:18.1.8-1
, from 18.1.8-1
The build file needed to be updated.
The package has been accidently pushed with llvm 19 into the stable multilib repository.
Pushing epoch to fix that issue
New MR !30865 just merged, mesa no longer have OMX frontend.
Add meson option gallium-omx
has been removed.
Same as dri3
, you'll need to remove the option to compile.
Meson option dri3
has been removed.
MR30952.
Build type: native build
mesa/meson.build:4:0: ERROR: Unknown options: "dri3"
A full log can be found at /tmp/makepkg/mesa-git/src/_build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
Aborting...
New vulkan layer screenshot
has been added to mesa.
@myghi63 : which llvm variant are you using and does this result in build failures ?
I only use mesa-minimal-git & lib32-mesa-minimal-git myself, and build mesa-git lib32-mesa-git when it's needed to troubleshoot.
Info from users of the packages like you helps a lot.
@hanzbadua: not a stupid question.
Archlinux repo package maintainers tend to enable everything and the kitchen sink in packages. I (and Reza seems to agree with that) only enable what is useful.
rusticl provides opencl and I am not aware of any 32-bit program that needs opencl so it's unneeded bloat. If you do have usecases for 32-bit opencl : please tell us and we'll look into it.
Perhaps a stupid question, but why does lib32-mesa in multilib provide a 32-bit version of rusticl however this package doesn't?
Pinned Comments
Lone_Wolf commented on 2024-02-14 11:49 (UTC)
Mesa commit b52e25d3 breaks intel iris & anv build UNLESS OpenCL support is present.
Incase you don't need those drivers, a temporary workaround is to disable them.
lib32-mesa-minimal-git is also affected.
Lone_Wolf commented on 2023-11-02 16:03 (UTC) (edited on 2023-11-02 16:05 (UTC) by Lone_Wolf)
@RPINerd in https://aur.archlinux.org/packages/lib32-mesa-git#comment-941648
Users of this package are supposed to (re)build lib32-mesa-git everytime mesa-git changes to avoid such issues.
I'm certain I have stated that in the past, but it may have been lost in the older pages of comments.
Lone_Wolf commented on 2019-05-09 13:30 (UTC)
This package now uses an environment variable to determine which llvm package it will be built against. Check PKGBUILD for details.