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.

@dragostini try setting the remote and pulling the commit to the makepkg branch

edit:

cd /var/tmp/pamac-build-dragostini/proton-ge-custom/src/proton-ge-custom/dxvk
git remote set-url origin https://github.com/doitsujin/dxvk.git
git pull origin d707c2eacd233876c82842fc79cda7b336a1f80d

@loathingkernel

Unfortunately my experience is a bit limited on git/github. I use it daily for work, but not in any way that would help you figure this out :(

The commit exists on github. I have no idea why it is happening.

@loathingkernel

I had done a fresh clone in a totally newly created directory, just to be safe.

@dragostini did you delete the existing clones?

EDIT: Hmm, nevermind, I just hit it too in a fresh clone. My archived clones had that commit.

@loathingkernel

built via terminal (git clone manually and makepkg -si) and it still borked. Same error.

fatal: git upload-pack: not our ref d707c2eacd233876c82842fc79cda7b336a1f80d

fatal: remote error: upload-pack: not our ref d707c2eacd233876c82842fc79cda7b336a1f80d

Fetched in submodule path 'dxvk', but it did not contain d707c2eacd233876c82842fc79cda7b336a1f80d. Direct fetching of that commit failed.

==> ERROR: A failure occurred in prepare().

Aborting...

[dragostini@crusnic01 proton-ge-custom]$

@dragostini That means that the commit the submodule is pointing to cannot be found. There are two reasons for it to happen, either it was deleted or the git clone was a shallow one. According to github the commit exists. Try again with makepkg and see if it happens.

@loathingkernel

Getting this:

Cloning into '/var/tmp/pamac-build-dragostini/proton-ge-custom/src/proton-ge-custom/dxvk'...

done.

fatal: git upload-pack: not our ref d707c2eacd233876c82842fc79cda7b336a1f80d

fatal: remote error: upload-pack: not our ref d707c2eacd233876c82842fc79cda7b336a1f80d

Fetched in submodule path 'dxvk', but it did not contain d707c2eacd233876c82842fc79cda7b336a1f80d. Direct fetching of that commit failed. ==> ERROR: A failure occurred in prepare().

Aborting...

Running Arch (technically EndeavourOS, but that is 99% pure Arch so I don't see how it should be an issue.)

Using Pamac for GUI AUR access / helper

@loathingkernel I actually tried both a full update to staging and just updating gcc and libraries after the git error. Same on both unfortunately. Last update to stable was on the 19th and they push updates looks like about every week and a half, so hopefully it'll hit in the next few days.

@stdinUsrError The error with cloning DXVK could be unrelated, or it could be related if you didn't do a full update on your system and just installed gcc. If you only installed gcc and its libs, you did what we call a partial update and your system might break in unexpected ways. Either do an update to Manjaro staging or revert to Manjaro stable and wait for it to catch up to Arch.