Package Details: mesa-git 17.1.0_devel.89867.7751ed39e4-1

Git Clone URL: https://aur.archlinux.org/mesa-git.git (read-only)
Package Base: mesa-git
Description: an open-source implementation of the OpenGL specification, git version
Upstream URL: http://mesa3d.sourceforge.net
Keywords: mesa X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-radeon
Provides: libva-mesa-driver, mesa, mesa-vdpau, opencl-driver, opencl-mesa, vulkan-driver, vulkan-intel, vulkan-radeon
Replaces: libva-mesa-driver, mesa, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-radeon
Submitter: Krejzi
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 148
Popularity: 2.550888
First Submitted: 2014-06-19 21:33
Last Updated: 2017-03-15 14:03

Required by (640)

Sources (2)

Pinned Comments

Lone_Wolf commented on 2016-10-11 20:52

Updated Pinned Comment

Recommended way to update :

run pacman -Syu
build & update llvm-svn & lib32-llvm-svn
build & update mesa-git
build & update lib32-mesa-git

If you feel llvm-svn takes to long to build (50 minutes on my system) Kerberizer (aur llvm-svn & lib32-llvm-svn maintainer ) has setup an unofficial repo.
see https://wiki.archlinux.org/index.php/Unofficial_user_repositories#llvm-svn

That repo is updated to latest llvm-svn several times per day.

Latest Comments

yurikoles commented on 2017-03-17 04:22

sandy8925, this package replaces most of mesa-related packages, see "replaces" verb in PKGBUILD

sandy8925 commented on 2017-03-17 04:19

Hello, it looks like following packages:
libva-mesa-driver, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-radeon

are now separate, and are not built as part of mesa. So, when I build mesa-git, none of the above package files are created like they were previously, and there are no -git versions of these packages in AUR.

Are these files part of the mesa-git package that gets created? How does this work?

Lone_Wolf commented on 2017-03-15 14:18

WARNING - MANUAL ACTION NEEDED

Mesa devs informed me that the server(s) hosting mesa trunk code are having trouble with the amount of work needed for git over http/https traffic and asked if i could switch back to git:// protocol.

I have changed the source uri.
On your next build makepkg will complain that the existing sourcefolder is not a valid clone.

cd into the folder where makepkg stores downloaded sourcefiles (it should have a folder called branches) .

run " git remote -v "
origin https://anongit.freedesktop.org/git/mesa/mesa.git (fetch)
origin https://anongit.freedesktop.org/git/mesa/mesa.git (push)

If your output differs, you're in wrong folder.

run " git remote set-url origin git://anongit.freedesktop.org/mesa/mesa "

run " git remote -v " again
origin git://anongit.freedesktop.org/mesa/mesa (fetch)
origin git://anongit.freedesktop.org/mesa/mesa (push)

Now makepkg will no longer complain.

Lone_Wolf commented on 2017-03-14 22:43

Thanks for the heads up , yurikoles .
patch removed.

yurikoles commented on 2017-03-14 15:27

Seems like disable-pthread-stubs-on-linux.patch is no longer needed since this commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=b82bd31c54cc91b972a027492fa75b13cd9c7267

Shugyousha commented on 2017-03-11 18:09

@Lone_Wolf: thanks, that did the trick! I knew that I would have to replace both lib32-mesa & mesa with their git counterparts at the same time but since the lib32-mesa-git depends on mesa-git which couldn't be installed, I did not manage to do it.

Ignoring dependencies with the -dd switch is something I would not recommend but in this case I don't think there was another way and it worked without a problem, thanks!

Lone_Wolf commented on 2017-03-11 17:37

@Shugyousha : you will have to replace lib32-mesa & mesa with their git counterparts at the same time.

If you build in a clean chroot this is a bit tricky, but doable.

If you build on a running system, use pacman -Rdd to remove all lib32-mesa-* parts you have installed.

After you have build & installed mesa-git, you can then build and install lib32-meas-git.

Lone_Wolf commented on 2017-03-11 17:29

I have looked into building aur mesa-git with libglvnd support, but the patches used in stock mesa 17.0.1-2 don't apply cleanly to git master .

For now aur mesa-git is sticking to the mesa-libgl symlink method.

Users that combine nvidia driver with this package may encounter problems.

Shugyousha commented on 2017-03-11 13:41

I get an unresolvable conflict with libglvnd when trying to mesa-git:

sudo pacman -U mesa-git-17.1.0_devel.89730.3d253d330a-1-x86_64.pkg.tar.xz mesa-libgl-git-17.1.0_devel.89730.3d253d330a-1-x86_64.pkg.tar.xz
loading packages...
resolving dependencies...
looking for conflicting packages...
:: mesa-git and mesa are in conflict. Remove mesa? [y/N] y
:: mesa-libgl-git and libglvnd are in conflict (libgles). Remove libglvnd? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-libglvnd: removing libglvnd breaks dependency 'libglvnd'

I could not find a way to solve this because mesa-git does not provide lbglvnd but does seem to conflict with it (and there are a lot of packages depending on libglvnd). Am I missing something obvious?

Lone_Wolf commented on 2017-03-11 12:17

@jugs : kerberizer is correct.
comment deleted.

All comments