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.

@cwrau I do not know why people are randomly getting this build issue with git-lfs, it is really not an issue with the PKGBUILD. Builds just fine in my clean-chroot CI https://github.com/loathingKernel/PKGBUILDs/actions/runs/8693427397

For the sake of clarity, the build happens in a brand new Arch Linux docker image every time, and anything installed in it (outside of implicit base-devel and multilib-devel metapackages) is controlled by the PKGBUILD's dependencies.

I can't build this, as the git-lfs is missing in the makedepends, could you add it?

Cloning into '/tmp/cwr/makepkg/proton-ge-custom/src/proton-ge-custom/gstreamer/subprojects/gst-integration-testsuites/medias'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (16/16), done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 54 (delta 0), reused 9 (delta 0), pack-reused 38
Receiving objects: 100% (54/54), 40.98 KiB | 207.00 KiB/s, done.
Resolving deltas: 100% (3/3), done.
remote: Enumerating objects: 1330, done.
remote: Counting objects: 100% (59/59), done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 1330 (delta 23), reused 42 (delta 18), pack-reused 1271
Receiving objects: 100% (1330/1330), 1.31 MiB | 400.00 KiB/s, done.
Resolving deltas: 100% (43/43), done.
git-lfs filter-process: line 1: git-lfs: command not found
fatal: the remote end hung up unexpectedly
fatal: Unable to checkout '06f5a5a9bad01b5cf76184aee4f430c834a9dac3' in submodule path 'gstreamer/subprojects/gst-integration-testsuites/medias'
fatal: Failed to recurse into submodule path 'gstreamer'
==> ERROR: A failure occurred in prepare().
    Aborting...
error: failed to build 'proton-ge-custom-2:GE.Proton9.4-1'

@loathingkernel That works. Thank you very much for your effort!

@CucumberSpace What can I do about a network issue on your side exactly?

  [28] Timeout was reached (Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds)

This looks obvious to me

@corax2.05 From latest pacman changelog

              - makepkg:
                - Add checksum support for git/mercurial/bzr sources

In the last release the checksums now also contain the sha256sum of the git repository.

Either wait for Manjaro to update pacman or edit the PKGBUILD and replace the checksum of the repository with 'SKIP'

error: failed to get `miniz_oxide` as a dependency of package `png v0.17.13`
    ... which satisfies dependency `png = "^0.17.2"` of package `gst-plugin-png v0.9.11 (/home/cucumbersp/.cache/yay/proton-ge-custom/src/proton-ge-custom/gst-plugins-rs/video/png)`

Caused by:
  failed to query replaced source registry `crates-io`

Caused by:
  download of mi/ni/miniz_oxide failed

Caused by:
  failed to download from `https://index.crates.io/mi/ni/miniz_oxide`

Caused by:
  [28] Timeout was reached (Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds)
==> ERROR: A failure occurred in prepare().

you are right, it's Manjaro. I cleand the folder and there is enough free space. System is up to date.

The build before some weeks runs fine.

The downloaded files in proton-ge-custom are: 0001-AUR-Pkgbuild-changes.patch 0002-AUR-Do-not-update-cargo-crates.patch 0003-AUR-Remove-kaldi-openfst-vosk-api-modules-because-of.patch 0004-AUR-Copy-DLL-dependencies-of-32bit-libvkd3d-dlls-int.patch 0005-AUR-Strip-binaries-early.patch 0006-AUR-Fix-hwnd-redefinition.patch PKGBUILD proton-ge-custom proton-ge-custom.install src wine-gecko-2.47.4-x86_64.tar.xz wine-gecko-2.47.4-x86.tar.xz wine-mono-9.0.0-x86.tar.xz I'm the owner and permissions are -rw-r--r-- The other files where found at the build... that seems strange.

When all else fails, try building in a clean chroot.

@xiota indeed the error looks weird, but if it was a download problem it would fail earlier when the git sources were updated, if it was a permissions problem it would also happen when the sources were pulled as git wouldn't be able to write them on disk. I do not know how it would behave if not enough free space was available, but I guess git would fail in this case too.

Given that the sources are in a folder named proton-ge-custom, if previous pacman checked only the checksum of files and not folders, it stands to reason to report that a "file" named proton-ge-custom was not found despite successfully downloading the sources.

The error message says the files/folders NOT FOUND. That is not a Manjaro problem. Most likely permissions, free space, or download problems.