Arch Linux User Repository

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.

• 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.

Sorry everyone, I forgot to change the version number to trigger rebuild at lilac. The lilac build bot will automatically update the version number tonight.

Exactly. I think I know how to fix the problem and I'm gonna test it, it's just an undefined reference error.

Edit: yep, as I suspected, the patch should be removed to let it build properly. I'm 99% that having dlopen instead of wine_dlopen, etc is completely unnecessary. I'll do some testing

Edit2: yeah there's no reason for the patch. dlopen, dlsym aren't deprecated in Wine anymore iirc? but it does work sooo

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.

• 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.

@damachine Please don't just post logs without reading them first and reading the comments in this thread. Your issue is that your afdko installation doesn't work. It has been discussed already multiple times. It is an issue with another package and the dependencies of that. I can't do anything about that because I don't maintain it. A few possible solutions have been posted in the comments.

Build error post a few lines before break:

File "/usr/lib/python3.8/site-packages/pkg_resources/init.py", line 770, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'defcon[lxml,pens]>=0.7.2' distribution was not found and is required by afdko make[1]: [../proton/build/makefile_base.mak:1532: obj-fonts/SourceHanSansSCRegular.otf] Fehler 1 make[1]: Verzeichnis „/tmp/makepkg/proton-native/src/build“ wird verlassen make: [../proton/build/makefile_base.mak:17: nested_make] Fehler 2 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... error making: proton-native

Yeah, it makes no sense to build (and ship) 5.0.9 if PKGBUILD states 5.1.13b as the version, so it's not only out-of-date but the package itself is broken. Either make pkgver 5.0.9 or provide a new version.

@xiretza the issue is in the PKGBUILD itself. It sources $_pkgver to download the source, which is still set to 5.0-9. .SRCINFO is autogenerated. Unless you have modified the PKGBUILD yourself, what you are building fine in a clean chroot is in fact the sources for 5.0-9

Package builds fine in a clean chroot here, maintainer simply forgot to update the source = in .SRCINFO, which causes the aurweb interface to show the old URL under "Sources".

@sperg512 Then what is the reasoning behind updating the version number?