Package Details: proton-ge-custom 2:GE.Proton9.22-1

Git Clone URL: https://aur.archlinux.org/proton-ge-custom.git (read-only, click to copy)
Package Base: proton-ge-custom
Description: Compatibility tool for Steam Play based on Wine and additional components, GloriousEggroll's custom build
Upstream URL: https://github.com/GloriousEggroll/proton-ge-custom
Keywords: dxvk proton steam valve vkd3d wine
Licenses: custom
Provides: proton
Submitter: loathingkernel
Maintainer: loathingkernel
Last Packager: loathingkernel
Votes: 40
Popularity: 2.15
First Submitted: 2020-03-23 23:52 (UTC)
Last Updated: 2024-12-30 14:02 (UTC)

Dependencies (117)

Required by (7)

Sources (12)

Pinned Comments

loathingkernel commented on 2023-10-12 10:43 (UTC) (edited on 2023-10-12 10:45 (UTC) by loathingkernel)

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

patlefort commented on 2022-09-22 00:33 (UTC)

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"

loathingkernel commented on 2020-11-21 10:28 (UTC) (edited on 2022-09-13 10:55 (UTC) by loathingkernel)

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.

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 34 Next › Last »

ms178 commented on 2022-05-18 13:17 (UTC) (edited on 2022-05-18 13:30 (UTC) by ms178)

@loathingkernel @pattlefort @dmfay

I also hit this error, starting with GCC 12.0.1. - I've traced it down to the following and related errors in the 32-bit ffmpeg build:

/libavcodec/x86/cabac.h:192:5: error: ‘asm’ operand has impossible constraints asm volatile( ^

These errors surprisingly don't stop the build process though and also see the build never finish with the reported process from @dmfay still running. Some Genotoo users did hit this issue in the past: https://bugs.gentoo.org/578802 - they solved it with "--disable-optimizations" in the configure options (https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6a2691a2bb66bd0497e458b0a00414507e8e99c0) but I could not test if that actually works in our case. Can someone prepare a patch which I could test?!

loathingkernel commented on 2022-05-18 08:25 (UTC) (edited on 2022-05-18 08:25 (UTC) by loathingkernel)

@dmfay @patlefort thank you for reporting it. I have hit the same issue, I am looking into it but haven't found a solution yet.

dmfay commented on 2022-05-16 20:01 (UTC)

I'm also seeing it hang in the ffmpeg build, 4h30m and counting on a Ryzen 9 5900X. Last few log lines:

i686-pc-linux-gnu-gcc -shared -Wl,-soname,libswscale.so.5 -Wl,-Bsymbolic -Wl,--version-script,libswscale/libswscale.ver -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat -Llibavresample -Llibavutil -Llibpostproc -Llibswscale -Llibswresample -Wl,-O1,--sort-common,--as-needed  -Wl,--as-needed -Wl,-z,noexecstack -Wl,--warn-common -Wl,-rpath-link=:libpostproc:libswresample:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil:libavresample  -o libswscale/libswscale.so.5 libswscale/alphablend.o libswscale/gamma.o libswscale/hscale.o libswscale/hscale_fast_bilinear.o libswscale/input.o libswscale/log2_tab.o libswscale/options.o libswscale/output.o libswscale/rgb2rgb.o libswscale/slice.o libswscale/swscale.o libswscale/swscale_unscaled.o libswscale/utils.o libswscale/vscale.o libswscale/x86/hscale_fast_bilinear_simd.o libswscale/x86/input.o libswscale/x86/output.o libswscale/x86/rgb2rgb.o libswscale/x86/rgb_2_rgb.o libswscale/x86/scale.o libswscale/x86/swscale.o libswscale/x86/yuv2rgb.o libswscale/x86/yuv_2_rgb.o libswscale/yuv2rgb.o -lavutil -lm -pthread -lva-drm -lva -lva-x11 -lva -lvdpau -lX11 -lm -lva -lXv -lX11 -lXext
/usr/bin/ld: libswscale/x86/hscale_fast_bilinear_simd.o: warning: relocation in read-only section `.text.unlikely'
/usr/bin/ld: warning: creating DT_TEXTREL in a shared object
cd ./libswscale/ && ln -s -f libswscale.so.5 libswscale.so

Stuck process cmdline:

> cat /proc/52048/cmdline
/usr/lib/gcc/x86_64-pc-linux-gnu/12.1.0/cc1-quiet-I.-Isrc/-imultilib32-MMDlibavcodec/h264_cabac.d-MFlibavcodec/h264_cabac.d-MTlibavcodec/h264_cabac.o-D_REENTRANT-D_ISOC99_SOURCE-D_FILE_OFFSET_BITS=64-D_LARGEFILE_SOURCE-D_POSIX_C_SOURCE=200112-D_XOPEN_SOURCE=600-DPIC-DZLIB_CONST-DHAVE_AV_CONFIG_H-DBUILDING_avcodecsrc/libavcodec/h264_cabac.c-quiet-dumpdirlibavcodec/-dumpbaseh264_cabac.c-dumpbase-ext.c-m32-mfpmath=sse-march=nocona-mtune=core-avx2-mno-avx2-mfpmath=sse-mstackrealign-mno-avx-gdwarf-2-gdwarf-2-gstrict-dwarf-g-O3-O3-O3-Wdeclaration-after-statement-Wall-Wdisabled-optimization-Wpointer-arith-Wredundant-decls-Wwrite-strings-Wtype-limits-Wundef-Wmissing-prototypes-Wno-pointer-to-int-cast-Wstrict-prototypes-Wempty-body-Wno-parentheses-Wno-switch-Wno-format-zero-length-Wno-pointer-sign-Wunused-const-variable=0-Wno-bool-operation-Wno-char-subscripts-Werror=format-security-Werror=implicit-function-declaration-Werror=missing-prototypes-Werror=return-type-Werror=vla-Wformat=1-Wno-maybe-uninitialized-std=c11-fdiagnostics-color=auto-ffile-prefix-map=/home/dian/.cache/pikaur/build/proton-ge-custom/src/build/src-ffmpeg=.-fwrapv-fno-strict-aliasing-ffile-prefix-map=/home/dian/.cache/pikaur/build/proton-ge-custom/src/build/src-ffmpeg=.-fomit-frame-pointer-fPIC-fno-math-errno-fno-signed-zeros-fno-tree-vectorize-o-%

patlefort commented on 2022-05-14 04:39 (UTC)

Build is freezing for me at this location:

cd ./libswscale/ && ln -s -f libswscale.so.5 libswscale.so
i686-pc-linux-gnu-strip -x libavcodec/x86/h264_intrapred.o
i686-pc-linux-gnu-strip -x libavcodec/x86/simple_idct.o

It stay there forever, I can see a cc1 process taking cpu time but it never ends.

loathingkernel commented on 2022-04-22 12:24 (UTC) (edited on 2022-04-22 12:25 (UTC) by loathingkernel)

@medzik Thank you for notifying me. I hastily posted the update because I am on vacation. I will try to update with the dependency, in the meantime you can manually add libvpx and lib32-libvpx in the depends array

medzik commented on 2022-04-22 11:07 (UTC)

ERROR: Dependency "vpx" not found, tried pkgconfig and cmake see logs

loathingkernel commented on 2022-04-18 19:42 (UTC) (edited on 2022-04-18 19:43 (UTC) by loathingkernel)

@saburouta it is required by the Proton package to build its fonts.

saburouta commented on 2022-04-18 18:53 (UTC)

Does one of these patches cause the build-step that invokes fontforge? I can build Wine without it. Is it a part of the Proton project itself, or did you add that? Can I disable that build-step somehow?

olean commented on 2022-02-24 15:43 (UTC)

hello, when running sekiro using the latest version of proton-ge-custom built using this package my xbox controller doesn't seem to work. my controller still works fine if i use one of steam's proton versions (i tried 6 and 7) with sekiro and other games using proton-ge-custom do seem able to use my controller. any idea what the problem could be?

nicman23 commented on 2022-02-16 09:28 (UTC)

huh you are right. well i just installed it manually and it worked. sorry to bother you :(

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 34 Next › Last »