You are not logged in.
vkdoom-git in the aur respository gives a build error
Sorry for making up another doom related issue in such a short period of time.
I am really a doom enthusiast, and this doom sourceport supports rtx raytracing
![]()
I tried on 2 different arch machines with the newest arch updates. It does not build on any of these 2 machines.
- The build errors at about 99%.
- Also the last time someone posted about a build error was me, and then some other guy in February. So it might be unmaintained.
- vkdoom-git should be similar to the gzdoom-git aur build instructions, cause vkdoom is a gzdoom fork
lto-wrapper: fatal error: make returned 2 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make[2]: *** [src/CMakeFiles/zdoom.dir/build.make:8834: vkdoom] Error 1
make[1]: *** [CMakeFiles/Makefile2:829: src/CMakeFiles/zdoom.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
make: Leaving directory '/home/oben/.cache/yay/vkdoom-git/src/vkdoom/build'
==> ERROR: A failure occurred in build().
Aborting...
-> error making: vkdoom-git-exit status 4
-> Failed to install the following packages. Manual intervention is required:
vkdoom-git - exit status 4
Last edited by mondlichtmann (2024-06-26 16:59:27)
Offline
/home/oben/.cache/yay/vkdoom-git/src/vkdoom/build'Does building with makepkg --log in a fresh folder give the same error ?
If yes, post the log files it creates .
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
If you want you can close this ticket/request, the features were mostly merged with gzdoom anyway.
Last edited by mondlichtmann (2024-06-27 11:12:09)
Offline
Closed is reserved for moderator actions , succesfull threads are usually marked by adding [Solved} to the title.
In this case you could use something like [Abandoned] or [Gave Up] .
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