Arch Linux User Repository

@rekman, thank you for looking into CUDA issues, at least it gives me an idea on how to fix it. That being said, my position remains to build it in a clean chroot, away from the locally installed packages. It is not feasible for me to carry patches for the build systems of various subprojects in the long run.

By enabling the 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of patch, you lose voice recognition which I assume is not that big of a loss as I haven't encountered a use for it, so I think it is an acceptable alternative.

Compilation will fail if you happen to have jwasm installed, due to vulkan loader. Workaround: uninstall jwasm or add this line to prepape() in the PKGBUILD:

sed -i 's/VULKAN_LOADER_CMAKE_ARGS = -DUSE_MASM=OFF/VULKAN_LOADER_CMAKE_ARGS = -DUSE_MASM=OFF -DJWASM_FOUND=0/' "$srcdir/$pkgname/Makefile.in"

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 tmpfs

• It 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 through steam-native).

• This PKGBUILD uses CFLAGS, CXXFLAGS and LDFLAGS hardcoded in the PKGBUILD itself. By default it uses the same C[XX]FLAGS as upstream, namely -march=nocona and -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.

• If you are not using CFLAGS and CXXFLAGS specific to your system this package won't offer much in terms of performance as the upstream build flags already target the nocona (Core2) architecture. It will possibly perform worse than upstream. The only benefits you get is not depending on steam linux runtime as well as linking to Arch libraries. If you still want to build it, you can uncomment the relevant lines in the PKGBUILD to enable CFLAGS and CXXFLAGS similar to the upstream.

• There have been reports with afdko failing 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 to afdko (or any of its python- dependencies, they are pulled in due to afdko and 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 the PROTON_USER_COMPAT_DATA env variable to 1.

• This package requires a Rust 32 bit target, please run rustup target install i686-unknown-linux-gnu BEFORE posting any issues if you're using rustup.

You need the afdko package.

I am having a make issue where it fails with makeotf: command not found any idea why?

The compile error should be fixed now.

Using Arch Linux, right after a fresh pacman -Syu, in a directory with a clean and fresh checkout of https://aur.archlinux.org/proton-ge-custom.git (ie., no altered C{,XX}FLAGS), running makepkg -fscCi results in this for me: http://sprunge.us/nTgGKj

After installing lld and today's commit that fixed the issue with the dxvk repo I'm happy to report the AUR build completed successfully for me with pamac on Manjaro.

@loathingkernel Thanks for getting the issues sorted and maintaining this package!

@randomguy343 I just updated it to pull the latest commit. But I do not want to to push it without testing it. You can grab the files from here and build it with makepkg. If it works, I will update the AUR versions.

Thanks for looking into it and no hurry, the Github releases are also easy to use in the mean time.

@randomguy343 Yeah, that is an issue with the github repo actually. It is weird, the commit exists but it is not part of any branch, so it doesn't get fetched. I am reluctant to re-target the dxvk submodule as GE applies patches on DXVK and I don't want to have to untangle any potential mess and I do not want to pin it. Generally with every release the submodule gets re-targeted. I will look into it when I find some time and see what I can do. Thanks for bringing it to my attention.

When installing using the AUR helper yay I get the following error, so I suppose it's a problem with the dxvk submodule's URL?
Thanks in advance for maintaining this package and helping with all the issues.


fatal: git upload-pack: not our ref 45cd4ce26882a07a4aca90fd771117789237e636
fatal: error at other end: upload-pack: not our ref 45cd4ce26882a07a4aca90fd771117789237e636
"fetch" in submodule-path 'dxvk' executed, but 45cd4ce26882a07a4aca90fd771117789237e636 not included.
Directly requesting this commit failed.
==> ERROR: An error happened in prepare().
Aborting...
error making: proton-ge-custom

@Dennis, thanks for figuring it out. I will add it as a dependency.