Package Details: mesa-git 24.3.0_devel.194818.d3429a7e00d.d41d8cd-1

Git Clone URL: https://aur.archlinux.org/mesa-git.git (read-only, click to copy)
Package Base: mesa-git
Description: an open-source implementation of the OpenGL specification, git version
Upstream URL: https://www.mesa3d.org
Keywords: mesa wayland X11
Licenses: custom
Conflicts: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-clover-mesa, opencl-rusticl-mesa, vulkan-intel, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Provides: libva-mesa-driver, mesa, mesa-libgl, mesa-vdpau, opencl-driver, opencl-rusticl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layers, vulkan-nouveau, vulkan-radeon, vulkan-swrast, vulkan-virtio
Submitter: Krejzi
Maintainer: rjahanbakhshi (Lone_Wolf)
Last Packager: Lone_Wolf
Votes: 182
Popularity: 0.46
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-09-15 20:40 (UTC)

Dependencies (53)

Required by (1302)

Sources (6)

Pinned Comments

Lone_Wolf commented on 2024-09-10 19:58 (UTC)

removed obsolete options, build now works again.

building opencl clover is disabled for now, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/11863

Those that need opencl should use rusticl instead. Note that rusticl at runtime is disabled by default, see https://docs.mesa3d.org/envvars.html#rusticl-environment-variables for info about enabling it.

Lone_Wolf commented on 2020-04-23 12:26 (UTC) (edited on 2023-03-30 07:04 (UTC) by Lone_Wolf)

Mesa and llvm are closely tied together. Everytime the llvm mesa is built against changes/updates , mesa needs to be rebuilt.

I expect anyone building mesa-git against one of the llvm trunk variants to be able to do that themselves, but atleast some of the people that built against repo llvm don't understand how to deal with such a rebuild.

The rest of this post is meant for those people.

  • Verify if latest PKGBUILD requirements match llvm repo versions.
  • If they don't , post to alert the maintainer of this.
  • DELAY the update of llvm/clang suite and their lib32- counterparts
  • Once the PKGBUILD does match, download it.

Option A - best one

  • run pacman -Syu to ensure your system is in sync with your mirrror server
  • build mesa-git in a clean chroot

see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot for the official way or https://aur.archlinux.org/packages/clean-chroot-manager for an alternative method.

  • install the newly built mesa-git
  • run pacman -Syu
  • ready

Option B - 2nd best

  • revert to repo mesa
  • pacman -Syu
  • build mesa-git
  • switch from mesa to mesa-git
  • ready

Lone_Wolf commented on 2019-07-09 13:43 (UTC) (edited on 2023-04-18 10:41 (UTC) by Lone_Wolf)

  • choosing which llvm variant to build against

WARNING : aur helpers don't support this method at all. They check .SRCINFO and that doesn't include this variable so it will use the default which is hardcoded to build against repo llvm.

Why would I want to use llvm development versions ?

For full functionality and latest features mesa trunk master needs to be build against llvm trunk master.
If you build against stable llvm things MAY work, but you're likely to lack some features and face stability issues.

Mesa-git uses a custom environment variable MESA_WHICH_LLVM for flexibility.
It has 4 values.
1 : aur llvm-minimal-git
2 : aur llvm-git
3: llvm-git from LordHeavy' unofficial repo
4: llvm from extra repo

I use value 1 95% of the time and set this in ~/.bash_rc .
If MESA_WHICH_LLVM is unset or empty, the default value of 4 (extra llvm) is used.

Lone_Wolf commented on 2018-01-30 14:06 (UTC) (edited on 2023-02-12 11:56 (UTC) by Lone_Wolf)

  • main difference with stable repo package
[extra]mesa is a split package, but aur mesa-git isn't.
Basically with aur mesa-git you get everything in one package, while [extra]/mesa allows you to leave out some parts if you don't want/need them.
Having a single package reduces maintenance and makes switching from stable to mesa-git rather easy, though reverting back to stable can be tricky.
  • meson settings
Those who compare PKGBUILDs will notice I don't use arch-meson, but meson setup.
I disagree with some of the settings made by arch-meson (especially the buildtype and enabling LTO by default) and feel using meson setup is cleaner.
  • how to update

run pacman Syu update non-repo packages for llvm if you use them

build mesa-git, log out , update mesa-git and restart X .

run glxinfo -B to verify basic OpenGL functionality

build lib32-mesa-git

run glxinfo32 -B to verify basic OpenGL functionality for multilib programs

Latest Comments

« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 .. 131 Next › Last »

nstgc commented on 2020-03-05 20:21 (UTC) (edited on 2020-03-05 20:28 (UTC) by nstgc)

@Lone_Wolf It's funny you should share that. I just remembered I fsck all received objects by default (set in --global). How embarrassing. It pulled now and is compiling. Thank you.

On a side note, I'd like to say how I appreciate that your package replaces four others. Helps take some of the guess work out.

Lone_Wolf commented on 2020-03-05 20:00 (UTC)

I found a stackoverflow post about that error, although the poster got the error with git push I do think it may be helpful .

https://stackoverflow.com/questions/56507791/remote-fatal-fsck-error-in-packed-object-when-pushing-oh-my-zsh-repo-to-new-re

nstgc commented on 2020-03-05 19:29 (UTC)

@Lone_Wolf Thank you. That seems to be working, however I'm still getting the same "...missingSpaceBeforeDate..." error, but this time on commit "c2908f1b53c841bfa450b066c6fa1ee78c2fdb85".

I know I'm really floundering with this and llvm (the -minimal-git version of which I have installed now thanks to your help), but I swear this is not the first time I've done something like this. I regularly install stuff from the AUR and I'm not using a helper which might make a mess of things. I use git extensively for work, and I've never had this particularly issue with any repo on any service. So I really have no clue what is going wrong. This is the only package I'm having this particular issue with.

And it's not just this build file. I tried git clone https://github.com/mesa3d/mesa.git with the same result.

$ git clone https://github.com/mesa3d/mesa.git
Cloning into 'mesa'...
remote: Enumerating objects: 1349, done.
remote: Counting objects: 100% (1349/1349), done.
remote: Compressing objects: 100% (610/610), done.
error: object c2908f1b53c841bfa450b066c6fa1ee78c2fdb85: missingSpaceBeforeDate: invalid author/committer line - missing space before date
fatal: fsck error in packed object
fatal: index-pack failed

Lone_Wolf commented on 2020-03-05 19:06 (UTC) (edited on 2020-03-05 19:09 (UTC) by Lone_Wolf)

Keep the git+ part, without it makepkg treats the download incorrectly.

nstgc commented on 2020-03-05 18:01 (UTC) (edited on 2020-03-05 18:05 (UTC) by nstgc)

I am still having trouble. I tried git remote set-url origin https://github.com/mesa3d/mesa.git, but that seems to do nothing (can't pull from repo). I then tried replacing https://gitlab.freedesktop.org/mesa/mesa.git in PKGBUILD with https://github.com/mesa3d/mesa.git, but then I MESA_WHICH_LLVM=1 makepkg -sir --cleanbuild I get:

==> Starting pkgver()...
/home/nstgc5/Installers/mesa-git.aur/PKGBUILD: line 82: cd: mesa: Not a directory
==> ERROR: A failure occurred in pkgver().
Aborting...

For some reason a file is being created named "mesa" in the root build directory.

The result of git diff -U1 looks like this:

 license=('custom')
-source=('mesa::git+https://gitlab.freedesktop.org/mesa/mesa.git'
+source=('mesa::https://github.com/mesa3d/mesa.git'
             'LICENSE')

nstgc commented on 2020-03-04 14:07 (UTC)

@YuriKoles Are you clean building or trying to pull the repo from scratch? Even when I try pulling outside of building (just go to a directory and git clone it myself) I get that error.

Thanks for the fixed repo.

yurikoles commented on 2020-03-04 08:02 (UTC)

@ntsgc

Tried to verify on my Arch just now and I see no such error with default repo.

yurikoles commented on 2020-03-04 07:41 (UTC)

@ntsgc

Please try switching PKGBUILD and your local clone to GitHub mirror, where error was fixed: https://github.com/mesa3d/mesa

nstgc commented on 2020-03-04 00:29 (UTC)

@yurikoles Thanks for explaining that. It's good to know it isn't just me, however I still don't know what I can do to fix this. I ran a google search, but none of the four results helped. I've never encountered something like this before. If this was my own repo I could go in and fix it, but it isn't so I have no idea how to clone it.

yurikoles commented on 2020-03-03 20:50 (UTC)

@nstgc This commit is very famous known to have problems since 2015, just search for hash in Google. In previous it broke pushing of mesa to GitHub and other hostings. But now It seems like recent update of Git also broke pulling as well.

« First ‹ Previous 1 .. 42 43 44 45 46 47 48 49 50 51 52 .. 131 Next › Last »