Package Details: mesa-minimal-git 24.3.0_devel.194673.5db135f66ad-2

Git Clone URL: https://aur.archlinux.org/mesa-minimal-git.git (read-only, click to copy)
Package Base: mesa-minimal-git
Description: an open-source implementation of the OpenGL specification, stripped down git version
Upstream URL: https://www.mesa3d.org
Licenses: MIT AND BSD-3-Clause AND SGI-B-2.0
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-vdpau, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layers, vulkan-radeon, vulkan-swrast, vulkan-virtio
Submitter: shoober420
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 11
Popularity: 0.005405
First Submitted: 2020-12-10 00:38 (UTC)
Last Updated: 2024-09-11 18:17 (UTC)

Required by (1209)

Sources (1)

Pinned Comments

Lone_Wolf commented on 2023-05-22 12:07 (UTC) (edited on 2024-09-06 21:16 (UTC) by Lone_Wolf)

Build order

llvm-minimal-git
spirv-headers-git
spirv-llvm-translator-minimal-git
libclc-minimal-git
mesa-minimal-git

N.B. these packages are closely tied together, make sure you build all of them in a short period of time (worst case on my system is around 3 hours) .

Build frequency

I aim to build everything (including the lib32 part) atleast once a week.

How often you build this is a personal choice, but once a month is in my opinion the absolute minimum .

In that timeframe mesa will have seen almost 1k commits, llvm/clang gets more.

Lone_Wolf commented on 2021-01-22 18:36 (UTC) (edited on 2021-01-22 18:39 (UTC) by Lone_Wolf)

Why does this package hard depend on llvm-minimal-git ?

  • performance

archlinux repo packages are build with -march=x86-64 -mtune=generic which works on lots of machines but makes limited use of modern processor capabilities. For many packages this has little impact, but with llvm my experience is different.

My local builds for llvm / mesa are done with -march=native and this has a noticeable effect on their performance.

How big the benefit of this is depends heavily on the exact hardware you use. Worse, the software setup also impacts this. The only way to find out if it benefits your system/software setup is to try it out yourself.

  • easier maintenance and troubleshooting

Since i started my first mesa trunk package late in 2010 I have maintained versions without any llvm, one llvm implementation, split versions, singular versions, versions supporting multiple llvm implementations , switch from libgl hacks libglvnd to allow mesa & nvidia to cooperate etc.

Depending on one llvm variant in a non-splitted singular version results in a simple PKGBUILD that is easy to maintain.

Troubleshooting is also much easier if maintainer uses the same llvm variant as users.

If people feel those reasons are not good enough to hard depend on llvm-minimal-git , maybe I should transfer ownership .

Lone_Wolf commented on 2021-01-09 15:02 (UTC)

Why does this exist ?

Basically mesa/mesa-git build almost everything they can build.

This package tries to build just enough so everyone can use it, but disables older and/or unused components.

Check https://bbs.archlinux.org/viewtopic.php?id=261629 for a discussion about this package.

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

ph34rb0t commented on 2024-12-31 01:49 (UTC) (edited on 2024-12-31 01:50 (UTC) by ph34rb0t)

Mesa-minimal (and other flavors) started building again for some reason. Maybe the downgrade and reinstall of rust (from "Extras") had some effect (I did not do anything else).

Lone_Wolf commented on 2024-12-29 10:29 (UTC) (edited on 2024-12-29 10:29 (UTC) by Lone_Wolf)

The gentoo ticket dooes seem relevant, but Archlinux rust package version is 1:1.83.0-1 , depends on llvm-libs 18.1.8-5 and works for me .

maybe there's something in your build environment that screws up things, please post the full build logs somewhere public .

ph34rb0t commented on 2024-12-28 21:22 (UTC) (edited on 2024-12-28 21:24 (UTC) by ph34rb0t)

Rebuilt your entire dependency chain with today's commits, but mesa-minimal-git still refuses to compile with the same Rust-related error message.

Looks like the Gentoo crowd also stumbles over this error: https://bugs.gentoo.org/946913 Seems to be related to Rust and LLVM versioning.

Lone_Wolf commented on 2024-12-27 21:37 (UTC)

ph34rb0t, no issues with mesa-minimal-git 25.0.0_devel.199475.5e4aeb3ad79-2 and llvm-libs-minimal-git 20.0.0_r522448.91bbebc7e118-1 built fresh just now.

Please try again.

Lone_Wolf commented on 2024-12-24 09:55 (UTC)

Thanks for report, will look at it end of the week.

ph34rb0t commented on 2024-12-23 20:46 (UTC) (edited on 2024-12-23 20:47 (UTC) by ph34rb0t)

Refuses to compile at the moment due to:

39752 | unsafe extern "C" { error: extern block cannot be declared unsafe --> src/gallium/frontends/rusticl/rusticl_mesa_bindings.rs:39755:1

d3vilguard commented on 2024-12-02 21:14 (UTC) (edited on 2024-12-07 06:23 (UTC) by d3vilguard)

Yep, same.

../mesa/src/compiler/clc/clc_helpers.cpp:844:24: error: no matching function for call to ‘clang::CompilerInstance::createDiagnostics(clang::TextDiagnosticPrinter*)’
  844 |    c->createDiagnostics(new clang::TextDiagnosticPrinter(

P.S. as of Dec 6 it compiled.

Lone_Wolf commented on 2024-12-02 20:31 (UTC)

The error is not visible in that snippet .

Are you seeing the error I reported in https://gitlab.freedesktop.org/mesa/mesa/-/issues/12223 ?

If not, post the whole build log somewehere public.

d3vilguard commented on 2024-12-02 11:26 (UTC)

Building fails (only building radeonsi,zink \ amd,swrast) 

[655/1741] Compiling C++ object src/compiler/glsl/libglsl.a.p/meson-generated_.._glsl_lexer.cpp.o  
[656/1741] Generating src/amd/common/sid_tables_h with a custom command (wrapped by meson to capture output)  
[657/1741] Compiling C++ object src/compiler/glsl/libglsl.a.p/builtin_functions.cpp.o  
[658/1741] Compiling C object src/compiler/nir/libnir.a.p/meson-generated_.._nir_opt_algebraic.c.o  
ninja: build stopped: subcommand failed.  
==> ERROR: A failure occurred in build().

Lone_Wolf commented on 2024-09-11 18:20 (UTC)

Thanks and confirmed.

Fixing was trickier then I hoped, but it works locally now.

Please try the latest (just uploaded) version.

1 2 3 4 5 6 .. 9 Next › Last »