You are not logged in.
amdonly-gaming-mesa-git compiles just fine but when I try compiling the lib32, it gets stuck and throws an error at the last linking step.
[1794/1794] Linking target src/gallium/targets/rusticl/libRusticlOpenCL.so.1.0.0
FAILED: src/gallium/targets/rusticl/libRusticlOpenCL.so.1.0.0
mold: fatal: src/gallium/frontends/rusticl/librusticl_proc_macros.so: incompatible file type: i386 is expected but got x86_64
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...
error: failed to build 'lib32-mesa-amdonly-gaming-git-24.1.0_devel.184875.893780b3625.d41d8cd98f00b204e9800998ecf8427e-1 (lib32-amdonly-gaming-libva-mesa-driver-git lib32-amdonly-gaming-mesa-git lib32-amdonly-gaming-mesa-vdpau-git lib32-amdonly-gaming-opencl-rusticl-mesa-git lib32-amdonly-gaming-vulkan-mesa-layers-git lib32-amdonly-gaming-vulkan-radeon-git lib32-amdonly-gaming-vulkan-swrast-git)':
error: packages failed to build: lib32-mesa-amdonly-gaming-git-24.1.0_devel.184875.893780b3625.d41d8cd98f00b204e9800998ecf8427e-1 (lib32-amdonly-gaming-libva-mesa-driver-git lib32-amdonly-gaming-mesa-git lib32-amdonly-gaming-mesa-vdpau-git lib32-amdonly-gaming-opencl-rusticl-mesa-git lib32-amdonly-gaming-vulkan-mesa-layers-git lib32-amdonly-gaming-vulkan-radeon-git lib32-amdonly-gaming-vulkan-swrast-git)
Edit: The issue I was having for half a week seems to have disappeared miraculously after system update that I did today.
Last edited by Yagato (2024-03-18 11:28:17)
Offline
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
mold: fatal: src/gallium/frontends/rusticl/librusticl_proc_macros.so: incompatible file type: i386 is expected but got x86_64
Next time try building with the default (gcc) ld linker. Incase that doesn't fail, you probably have found a bug in mold .
Please pepend [Solved} to the thread title (edit first post)
Last edited by Lone_Wolf (2024-03-18 11:09:58)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline