Package Details: lib32-mesa-git 24.3.0_devel.192477.76ae27efb3c.d41d8cd-1

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: 45
Popularity: 0.150810
First Submitted: 2009-12-18 18:42 (UTC)
Last Updated: 2024-07-31 06:18 (UTC)

Required by (92)

Sources (3)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 32 Next › Last »

rjahanbakhshi commented on 2022-07-03 11:38 (UTC)

@artefact,

I'm not exactly sure why lib32-mesa-libgl wasn't provided by this package since the multilib/lib32-mesa does provide it. I added it and it seems to be alright. Maybe @Lone_Wolf knows why it was like that.

artefact commented on 2022-07-03 09:51 (UTC)

mesa-git provides mesa-libgl, but lib32-mesa-git doesn't provide lib32-mesa-libgl. Is there a good reason for this? This breaks building a few packages, eg wine-ge-custom.

Billli11 commented on 2022-07-02 21:06 (UTC) (edited on 2022-07-02 21:20 (UTC) by Billli11)

lib32-llvm and lib32-llvm-libs in official multilab repo has been updated to 14.0.6-1

https://archlinux.org/packages/multilib/x86_64/lib32-llvm/

Please update the PKGBUILD file.

Thanks

rjahanbakhshi commented on 2022-03-23 20:46 (UTC)

@kogasa

I was adding the patch but noticed it's already applied upstream. So no need to do anything here.

kogasa commented on 2022-03-23 19:31 (UTC)

missing-include.patch from mesa-git is necessary and sufficient to build with llvm 15.

sir_randomuser commented on 2022-03-13 17:00 (UTC)

@Grimish

I've created a simple bash script to build mesa-git and lib32-mesa-git in a clean CHROOT, you may find it useful. Link: https://github.com/SirToffski/mesa-git-arch

It relies on using clean-chroot-manager. Very convenient - as it will automatically update the local repository with packages it builds. https://github.com/graysky2/clean-chroot-manager

Lone_Wolf commented on 2022-03-11 09:46 (UTC) (edited on 2022-03-11 09:52 (UTC) by Lone_Wolf)

clean chroot builds do require some additional setup, yes.

Below is how it goes with multilib-build from devtools package .

  • I have never found a way to pass an env var to multilib-build , set the value you want explicitly very early in the PKGBUILD (before it's used)

  • You have to pass every non-repo pacakge explicitly to the command using the -I option used by makechrootpkg .

multilib-build -- -I /path/to/package1.pkg.tar.zst -I /path/to/pacakge2.tar.zst

  • for lib32-mesa-git with MESA_WHICH_LLVM=1 you need to add 5 pacakge tarballs : llvm-libs-minimal-git , llvm-minimal-git , mesa-git , lib32-llvm-libs-minimal-git and lib32-llvm-minimal-git .

  • putting those in a script is tricky, as you have to include the correct version.

NOTE: the above also applies to mesa-git in a chroot, if you don't set MESA_WHICH_LLVM explicitly it will default to 4 and use repo llvm.

https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot has some imfo.

Grimish commented on 2022-03-10 22:09 (UTC)

Maybe i'm doing something wrong - haven't done much building in recent years so I'll jump to the chase. I build mesa-git in a clean chroot, everything works out. When I attempt to do lib32-mesa-git I run into a dependancy issue using MESA_WHICH_LLVM=1. Have not attempted any other version. I was thinking though that somehow that mesa-git has to be utilized or installed to the chroot as its mentioned among like 8 other 32-bit library dependants that pacman cannot resolve. I do enable the multilib repository in pacman as well. Not sure if thats what I'm missing. Maybe someone can help me out with that or point me in the right direction.

Thanks.

sir_randomuser commented on 2022-03-09 20:14 (UTC)

@rjahanbakhshi

Thank you!

Regarding moving lib32-libglvnd from makedepends() to depends() - not sure if that was the fix anymore. It compiled correctly once yesterday - but the more I think about it - maybe I accidentally left MESA_WHICH_LLVM undefined that time, so it used the packages from extra. Was not able to successfully compile it again.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 32 Next › Last »