Multiple times I have tried to build this, with yay and a manual build. Here is the same error I get every time. Let me know if I can provide anything else to help resolve this.
../src-wine/dlls/d3d12/d3d12_main.c: In function ‘D3D12CreateDevice’:
../src-wine/dlls/d3d12/d3d12_main.c:341:10: error: ‘const struct vkd3d_application_info’ has no member named ‘api_version’; did you mean ‘engine_version’?
341 | .api_version = VKD3D_API_VERSION_1_2,
| ^~~~~~~~~~~
| engine_version
../src-wine/dlls/d3d12/d3d12_main.c:341:24: error: ‘VKD3D_API_VERSION_1_2’ undeclared (first use in this function); did you mean ‘VK_API_VERSION_1_2’?
341 | .api_version = VKD3D_API_VERSION_1_2,
| ^~~~~~~~~~~~~~~~~~~~~
| VK_API_VERSION_1_2
../src-wine/dlls/d3d12/d3d12_main.c:341:24: note: each undeclared identifier is reported only once for each function it appears in
make[3]: *** [Makefile:48312: dlls/d3d12/d3d12_main.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/joe/.cache/yay/proton/src/build/obj-wine32'
make[2]: *** [../proton/Makefile.in:734: /home/joe/.cache/yay/proton/src/build/.wine-build32] Error 2
make[2]: Leaving directory '/home/joe/.cache/yay/proton/src/build'
make[1]: *** [../proton/Makefile.in:121: container-build] Error 2
make[1]: Leaving directory '/home/joe/.cache/yay/proton/src/build'
make: *** [../proton/Makefile.in:32: nested_make] Error 2
==> ERROR: A failure occurred in build().
Aborting...
-> error making: proton
Pinned Comments
loathingkernel commented on 2020-10-22 08:43 (UTC) (edited on 2022-06-15 14:11 (UTC) by loathingkernel)
Notes about this package
If you encounter issues while using this package, please contact me here first before reporting an issue to the upstream repository. Don't post logs, link to them. If you are using Manjaro, another derivative or an AUR helper, please mention it, I DO NOT TEST AGAINST THEM AND I CANNOT KNOW WHAT MIGHT BE WRONG WITH THE DISTRO/HELPER OF YOUR CHOICE.
It takes a LOT of time and space to build. Building with multiple jobs helps but might cause builds to fail in rare cases. Be sure to have at least 16GB of RAM if you are building on
tmpfsIt is NOT built against
Steam Linux Runtime (Sniper, Soldier, etc)and as such it doesn't require it. Still, is detected by Steam and works properly (preferable throughsteam-native).This PKGBUILD uses
CFLAGS,CXXFLAGSandLDFLAGShardcoded in the PKGBUILD itself. By default it uses the sameC[XX]FLAGSas upstream, namely-march=noconaand-mtune=core-avx2. To change them you will have to edit the PKGBUILD itself. Due to the nature of this package some flags can cause it to fail to build or not function properly. I try to filter them out but it is based on testing. If you have a feeling that compile-time options are involved in the issues you are having please include them in your comment. Currently the filtered options are-fstack-protector-{,-strong,-all}(dxvk and vkd3d only),-fno-plt,-z,relro,-z,now. Also the use of AVX instructions is disabled through-mno-avx.There have been reports with
afdkofailing to find its dependencies during building. I can't do anything about that as I don't maintain that package. It is NOT an issue with this package and I haven't found a way to not depend on it. Please don't report fails due toafdko(or any of itspython-dependencies, they are pulled in due toafdkoand only used by that), it has been discussed enough. There are possible workarounds in the comments.It contains a patch to store game prefixes in the main Steam Library under
$HOME/.local/share/Steam/steamapps/compatdata. It helps with isolation of game prefixes between users and works around issues with shared libraries on NTFS partitions due to drive symlinks. To enable it, set thePROTON_USER_COMPAT_DATAenv variable to1.This package requires a Rust 32 bit target, please run
rustup target install i686-unknown-linux-gnuBEFORE posting any issues if you're usingrustup.