Compiling 20.1.0_devel.120094.23037627359
fails with the following error
Linking target src/vulkan/overlay-layer/libVkLayer_MESA_overlay.so.
FAILED: src/vulkan/overlay-layer/libVkLayer_MESA_overlay.so
g++ -m32 -o src/vulkan/overlay-layer/libVkLayer_MESA_overlay.so 'src/vulkan/overlay-layer/5cf59b8@@VkLayer_MESA_overlay@sha/overlay.cpp.o' 'src/vulkan/overlay-layer/5cf59b8@@VkLayer_MESA_overlay@sha/overlay_params.c.o' -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libVkLayer_MESA_overlay.so -march=znver1 -mtune=znver1 -O2 -pipe -fno-plt -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now src/vulkan/util/libvulkan_util.a src/util/libmesa_util.a src/util/format/libmesa_format.a src/imgui/libimgui_core.a -Wl,-Bsymbolic-functions -Wl,-z,relro /usr/lib32/libz.so -pthread -lm /usr/lib32/libxcb.so /usr/lib32/libX11-xcb.so /usr/lib32/libX11.so /usr/lib32/libxcb-dri2.so /usr/lib32/libxcb-dri3.so /usr/lib32/libxcb-present.so /usr/lib32/libxcb-sync.so /usr/lib32/libxshmfence.so /usr/lib32/libwayland-client.so /usr/lib32/libdrm.so /usr/lib32/libxcb-randr.so /usr/lib32/libXrandr.so -ldl /usr/lib/libzstd.so -Wl,--end-group '-Wl,-rpath,$ORIGIN/../util:$ORIGIN/../../util:$ORIGIN/../../util/format:$ORIGIN/../../imgui' -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/vulkan/util -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/util -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/util/format -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/imgui
/usr/bin/ld: /usr/lib/libzstd.so: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
[455/1443] Generating amdgfxregs_h with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
I then set vulkan-overlay-layer
in the PKGBUILD to false
thinking it might be an issue with that
-D vulkan-overlay-layer=false \
and then the following error showed
Linking target src/gbm/libgbm.so.1.0.0.
FAILED: src/gbm/libgbm.so.1.0.0
gcc -m32 -o src/gbm/libgbm.so.1.0.0 'src/gbm/cd6bfad@@gbm@sha/main_backend.c.o' 'src/gbm/cd6bfad@@gbm@sha/main_gbm.c.o' 'src/gbm/cd6bfad@@gbm@sha/backends_dri_gbm_dri.c.o' -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libgbm.so.1 -march=znver1 -mtune=znver1 -O2 -pipe -fno-plt -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now src/loader/libloader.a src/util/libmesa_util.a src/util/format/libmesa_format.a src/util/libxmlconfig.a -Wl,--gc-sections /usr/lib32/libdrm.so /usr/lib32/libwayland-server.so -ldl -pthread /usr/lib32/libz.so -lm /usr/lib32/libexpat.so /usr/lib/libzstd.so -Wl,--end-group '-Wl,-rpath,$ORIGIN/../loader:$ORIGIN/../util:$ORIGIN/../util/format' -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/loader -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/util -Wl,-rpath-link,/home/user/pkg/aur_arch_builds/lib32-mesa-git/src/_build/src/util/format
/usr/bin/ld: /usr/lib/libzstd.so: error adding symbols: file in wrong format
collect2: error: ld returned 1 exit status
[746/1434] Generating sid_tables_h with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
so I enabled vulkan-overlay-layer
again and set zstd
to false
thinking it might be something to do with zstd
-D zstd=false \
and now it compiles successfuly
the mesa-git
64bit package compiles fine with zstd set to auto
or true
or false
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.