Package Details: mesa-git 24.1.0_devel.188033.40f39482e15.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-clover-mesa, 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: rjahanbakhshi
Votes: 177
Popularity: 1.63
First Submitted: 2014-06-19 21:33 (UTC)
Last Updated: 2024-04-17 22:44 (UTC)

Dependencies (50)

Required by (1233)

Sources (6)

Pinned Comments

Lone_Wolf commented on 2024-04-03 16:59 (UTC)

To those with the directx errors : archlinux directx-headers pacakgae is 2 releases behind upstream. Try building against aur directx-headers-git .

I don't remember what d3d12 does, but offical mesa also supports it.

@ZephyrCheez : thanks, that option lead to meson subprojects and mesa sourcetree does appear to include the data needed to use them. Adding nouveau vulkan looks doable now, no idea when there will be time to implement it.

Lone_Wolf commented on 2024-02-20 00:09 (UTC) (edited on 2024-02-20 00:11 (UTC) by Lone_Wolf)

@Beiruty, those have the same cause as the other recent build failures : changes in intel drivers.

The build issues caused by changes in intel drivers are now solved for MESA_WHICH_LLVM 1, 3 and 4 (llvm-minimal-git , llvm from lordheavy unofficial repo and offical repo llvm )

MESA_WHICH_LLVM 2 (aur llvm-git) build is still broken, but I MAY have a solution for that without having to create new packages.

The good news is that once all 4 variants built again, only minor changes should be needed to add opencl clover & opencl rusticl support.

(A lot of the work required to built the intel drivers is also useful for clover & rusticl)

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 2 3 4 5 6 7 8 9 10 11 .. 124 Next › Last »

ArchUsr1 commented on 2024-01-31 22:18 (UTC) (edited on 2024-02-04 03:47 (UTC) by ArchUsr1)

I can confirm, after disabling LTO everything works again.

For anyone interested do: paru -S mesa-git --fm vim

and edit PKGBUILD then set -D b_lto=true to false

deemon commented on 2024-01-31 21:53 (UTC)

@Lone_wolf yes it did, but not anymore... since Timeshifting back also rolled journald back :D But pretty much exactly that happened what ArchUsr1 commented on. Am using Plasma Wayland and after bootup there was black screen and only mouse. CTRL-ALT-F3 and logged into terminal and checked journald and it did show sddm crash.

Beiruty commented on 2024-01-31 20:28 (UTC)

The bug I am seeing is described here: https://bugzilla.redhat.com/show_bug.cgi?id=2262065

ArchUsr1 commented on 2024-01-31 18:04 (UTC)

Looks like kwin wayland is crashing since yesterday. SDDM works if it uses X11, but after login in with wayland session screen is black and only cursor is visible SDDM will crash if configured with wayland as well I've created an issue in mesa, but I'm not sure if some latest mesa update causing this issue or some package https://gitlab.freedesktop.org/mesa/mesa/-/issues/10536

Lone_Wolf commented on 2024-01-31 17:59 (UTC)

Latest comments in https://gitlab.freedesktop.org/mesa/mesa/-/issues/6376 indicate lto may still have issues.

Beiruty, I suggest you disable lto again, re-buoild and test.

Beiruty commented on 2024-01-31 17:21 (UTC) (edited on 2024-01-31 17:23 (UTC) by Beiruty)

I used $NINJAFLAGS="-j8" And the load went to 56 with firefox. I closed firefox and load stabilized at 24 Prior to "lto1-tran" builds, build time on my machine was 8-mins. Now, it is 17-mins. I let the build completes, and I restarted my machine, I am still seeing incomplete renderings of pixelated images such as user icons, taskmanger preview icons and flicking at the Plasma top panel. It looks like a regression.

I restored to before mesa-git upgrade.

└─(11:20:42)──> glxinfo -B ──(Wed,Jan31)─┘ name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: AMD (0x1002) Device: AMD Radeon HD 7800 Series (radeonsi, pitcairn, ACO, DRM 3.56, 6.7.2-x64v2-xanmod1) (0x6818) Version: 24.1.0 Accelerated: yes Video memory: 2048MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 Memory info (GL_ATI_meminfo): VBO free memory - total: 1018 MB, largest block: 1018 MB VBO free aux. memory - total: 7637 MB, largest block: 7637 MB Texture free memory - total: 1018 MB, largest block: 1018 MB Texture free aux. memory - total: 7637 MB, largest block: 7637 MB Renderbuffer free memory - total: 1018 MB, largest block: 1018 MB Renderbuffer free aux. memory - total: 7637 MB, largest block: 7637 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 2048 MB Total available memory: 9983 MB Currently available dedicated video memory: 1018 MB OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon HD 7800 Series (radeonsi, pitcairn, ACO, DRM 3.56, 6.7.2-x64v2-xanmod1) OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.0-devel (git-8ff3a13e4d) OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.0-devel (git-8ff3a13e4d) OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.0-devel (git-8ff3a13e4d) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Lone_Wolf commented on 2024-01-31 16:27 (UTC)

LTO builds do increase buildtime and memory & IO resources used at buildtime in exchange for runtime performance improvements. Also ninja is known to be resource greedy .

options to mitigate the load :

  • prepend NINJAFLAGS="-j N -l N" to the build command (replace N with the number of threads you're willing to use for compiling)

  • If you have < 32 GiB memory, consider settting TMPDIR to a location on a SSD (preferably one on a different controller). This slows down the build some, but reduces the memory and IO pressure substantially.

Beiruty commented on 2024-01-31 11:31 (UTC)

I have a 4-core 8-Thread intel CPU, 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz When building mesa, average load tops around 8-9. Another new observation, now building mesa is out of control, average load is going up to 23-24 slowing the build.

https://photos.onedrive.com/share/8967D5A2C9DBD83D!23830?cid=8967D5A2C9DBD83D&resId=8967D5A2C9DBD83D!23830&authkey=!AO67OmTlDqTIA0g&ithint=photo&e=RfcpIa

Beiruty commented on 2024-01-31 10:41 (UTC) (edited on 2024-01-31 10:43 (UTC) by Beiruty)

└─(04:38:14)──> sudo pacman -Fy 1 ↵ ──(Wed,Jan31)─┘ :: Synchronizing package databases... endeavouros 141.9 KiB 500 KiB/s 00:00 100% core-testing 722.4 KiB 1704 KiB/s 00:00 100% core 1060.5 KiB 2.42 MiB/s 00:00 100% extra-testing 1630.3 KiB 3.37 MiB/s 00:00 100% extra 39.1 MiB 36.7 MiB/s 00:01 100% multilib-testing 2.3 KiB 12.4 KiB/s 00:00 100% multilib 209.3 KiB 595 KiB/s 00:00 100%

└─(04:38:20)──> pacman -F libKF5GuiAddons.so.5 ──(Wed,Jan31)─┘ extra/kguiaddons5 5.114.0-1 (kf5) [installed] usr/lib/libKF5GuiAddons.so.5

I will make a full backup and try again to install latest mesa-git

Lone_Wolf commented on 2024-01-31 09:52 (UTC) (edited on 2024-01-31 09:52 (UTC) by Lone_Wolf)

That doesn't look like it's related to mesa-git.

run pacman -Fy with root rights, then pacman -F libKF5GuiAddons.so.5 to see which package that lib belongs to and whether you have it installed.

on archlinux it's in kguiaddons5 which is needed for gwenview, krusader and a few others.

If you don't have any of those you could change sddm to run under wayland instead of X. see https://wiki.archlinux.org/title/SDDM#Running_under_Wayland

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