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.

What is in your MAKEFLAGS? I am not doing any filtering, so the specified value after -j can be the problem. Could you hardcode the SUBJOBS variable in the PKGBUILD to any value you would like and try again?

The thing is if I revert to how the original makefile is doing it, different subprojects get built at the same time so logging is interleaved. Also every meson subproject will spawn an equal amount of jobs as there is no communication between the makefile and the meson build systems.

That being said, I will try to filter MAKEFLAGS if that is the issue.

Downgraded meson, but:

:: building 32bit gst_orc...
env CARGO_HOME=/home/main-builder/pkgwork/src/build/.cargo CARGO_TARGET_I686_UNKNOWN_LINUX_GNU_LINKER="gcc" CARGO_TARGET_I686_UNKNOWN_LINUX_GNU_RUSTFLAGS="" CCACHE_BASEDIR="/home/main-builder/pkgwork/src/build/src-gst_orc" STRIP="strip" CC=" gcc -m32" CXX=" g++ -m32" LD="i686-linux-gnu-ld" PKG_CONFIG="i686-pc-linux-gnu-pkg-config" CROSSCC=" i686-w64-mingw32-gcc" CROSSCXX=" i686-w64-mingw32-g++" CROSSLD="i686-w64-mingw32-ld" CROSSPKG_CONFIG="i686-pc-linux-gnu-pkg-config" PATH=":/home/main-builder/pkgwork/src/proton-ge-custom/glslang/bin:$PATH" LD_LIBRARY_PATH="$LD_LIBRARY_PATH" PKG_CONFIG_PATH="" CFLAGS="  -gdwarf-2 -gstrict-dwarf -O3 -march=nocona -mtune=core-avx2 -pipe -mno-avx -mfpmath=sse -fwrapv -fno-strict-aliasing -ffile-prefix-map=/home/main-builder/pkgwork/src/build/src-gst_orc=. -mstackrealign" CXXFLAGS="  -gdwarf-2 -gstrict-dwarf -O3 -march=nocona -mtune=core-avx2 -pipe -mno-avx -mfpmath=sse -fwrapv -fno-strict-aliasing -ffile-prefix-map=/home/main-builder/pkgwork/src/build/src-gst_orc=. -mstackrealign -std=c++17" LDFLAGS="   -Wl,-O1,--sort-common,--as-needed" ninja -j -C "/home/main-builder/pkgwork/src/build/obj-gst_orc32" install -v
ninja: fatal: invalid -j parameter
make[2]: *** [../proton-ge-custom/build/makefile_base.mak:435: /home/main-builder/pkgwork/src/build/.gst_orc-build32] Error 1

Thanks for the update!

While we are waiting for loathingkernel to find time to update the PKGBUILD, anyone managed to make a functioning one for the latest Proton GE version that they could share with me? Tried to edit the PKGBUILD myself, but what was required was beyond my ability as it wasn't just as simple as changing commits and such. Would appreciate it.

In the mean time, people might be interested to know that an prebuilt alternative also exists on AUR, though it's build against steam linux runtime if I am not mistaken.

@markkuit yes, it would be absolutely fine to edit it out until you have pacman 6. I cannot comment on any other potential issues from reading the thread you linked.

@loathingkernel thank you; for Manjaro users passing by, it looks like pacman is still at v5 due to ongoing pamac porting (see forum thread for more info).

Would it be safe (and working) to edit out the !lto option from the PKGBUILD when building, as a temporary fix for the time being?

@markkuit yes, you are missing core/pacman 6.0.0-2

With the addition of !lto in the options array in commit f304e64fbdfa ("Fix compilation error due to missing <optional> include"), this fails at the very beginning with: ==> ERROR: options array contains unknown option '!lto'.

This is on Manjaro, libalpm v12.0.2, Pacman v5.2.2, tried with Pamac 10.0.6-2 and yay v10.2.2. Am I missing something?

@Nullrequest afdko should be installed by pip during the prepare step, I have confirmed this multiple times. Is there any special configuration around your system? Can you post a link to your build log?