| Git Clone URL: | https://aur.archlinux.org/wine-ge-custom.git (read-only, click to copy) |
|---|---|
| Package Base: | wine-ge-custom |
| Description: | A compatibility layer for running Windows programs - GloriousEggroll branch |
| Upstream URL: | https://github.com/GloriousEggroll/wine-ge-custom |
| Licenses: | LGPL |
| Conflicts: | wine |
| Provides: | wine |
| Submitter: | loathingkernel |
| Maintainer: | loathingkernel |
| Last Packager: | loathingkernel |
| Votes: | 35 |
| Popularity: | 1.66 |
| First Submitted: | 2021-09-01 22:06 (UTC) |
| Last Updated: | 2023-12-02 12:26 (UTC) |
I don't know what shitty things yay is doing and why but it doesn't follow the assumed makepkg way and it doesn't retain the environment between prepare() and build() as evident by the existence of filtered flags in your log. My guess is that it first prepares the sources and then starts the build again with a new environment for some reason.
Package builds fine in a clean chroot with Arch's proper tooling.
@kenga what distro are you on and are you using a helper? Try without a helper and if it persists, report back.
Fails for me without without any modifications of the PKGBUILD as well (6.18.GE.1-1, PKGBUILD commit a7aae53a9ff4)
<command-line>: warning: "_FORTIFY_SOURCE" redefined
<command-line>: note: this is the location of the previous definition
/home/user/.cache/yay/wine-ge-custom/src/wine-ge-custom-64-build/tools/winebuild/winebuild -w --def -o dlls/kernel32/libkernel32.def \
-m32 --export ../wine-ge-custom/wine/dlls/kernel32/kernel32.spec
/home/user/.cache/yay/wine-ge-custom/src/wine-ge-custom-64-build/tools/winegcc/winegcc -o dlls/capi2032/capi2032.dll.so \
--wine-objdir . --winebuild \
/home/user/.cache/yay/wine-ge-custom/src/wine-ge-custom-64-build/tools/winebuild/winebuild -m32 \
-fno-PIC -Wl,-z,notext -fasynchronous-unwind-tables -shared \
../wine-ge-custom/wine/dlls/capi2032/capi2032.spec -mcygwin dlls/capi2032/cap20wxx.o \
libs/port/libwine_port.a -ldl -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
/usr/bin/ld: dlls/capi2032/cap20wxx.o: direct GOT relocation R_386_GOT32X against `__wine_dbg_header' without base register can not be used when making a shared object
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/gcc failed
make: *** [Makefile:16025: dlls/capi2032/capi2032.dll.so] Error 2
==> ERROR: A failure occurred in build().
Aborting...
error making: wine-ge-custom
@idle_zealot, you are having trouble because you edited the PKGBUILD without reading the comments.
I'm also having trouble building this.
<command-line>: warning: "_FORTIFY_SOURCE" redefined
<command-line>: note: this is the location of the previous definition
rm -f libs/port/libwine_port.a && ar rc libs/port/libwine_port.a \
libs/port/getopt.o libs/port/lstat.o libs/port/mkstemps.o libs/port/poll.o libs/port/pread.o \
libs/port/pwrite.o libs/port/readlink.o libs/port/spawn.o libs/port/symlink.o && ranlib libs/port/libwine_port.a
/home/user/.cache/yay/wine-ge-custom/src/wine-ge-custom-64-build/tools/winegcc/winegcc -o dlls/avicap32/avicap32.dll.so \
--wine-objdir . --winebuild \
/home/user/.cache/yay/wine-ge-custom/src/wine-ge-custom-64-build/tools/winebuild/winebuild -m32 \
-fno-PIC -Wl,-z,notext -fasynchronous-unwind-tables -shared \
../wine-ge-custom/wine/dlls/avicap32/avicap32.spec dlls/avicap32/avicap32_main.o \
libs/port/libwine_port.a -ldl -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
/usr/bin/ld: dlls/avicap32/avicap32_main.o: direct GOT relocation R_386_GOT32X against `__wine_dbg_header' without base register can not be used when making a shared object
collect2: error: ld returned 1 exit status
winegcc: /usr/bin/gcc failed
make: *** [Makefile:13451: dlls/avicap32/avicap32.dll.so] Error 2
==> ERROR: A failure occurred in build().
Aborting...
error making: wine-ge-custom
Can't reproduce it, what version of vkd3d are you using?
Having problems building this, seems there is a naming problem, any ideas?
../wine-ge-custom/wine/dlls/d3d12/d3d12_main.c:346:10: error: ‘const struct vkd3d_application_info’ has no member named ‘api_version’; did you mean ‘engine_version’? 346 | .api_version = VKD3D_API_VERSION_1_2, | ^~~~~~~~~~~ | engine_version ../wine-ge-custom/wine/dlls/d3d12/d3d12_main.c:346:24: error: ‘VKD3D_API_VERSION_1_2’ undeclared (first use in this function); did you mean ‘VK_API_VERSION_1_2’? 346 | .api_version = VKD3D_API_VERSION_1_2, | ^~~~~~~~~~~~~~~~~~~~~ | VK_API_VERSION_1_2 ../wine-ge-custom/wine/dlls/d3d12/d3d12_main.c:346:24: note: each undeclared identifier is reported only once for each function it appears in make: *** [Makefile:29593: dlls/d3d12/d3d12_main.o] Error 1 ==> ERROR: A failure occurred in build(). Aborting...
Pinned Comments
loathingkernel commented on 2022-03-02 14:12 (UTC)
@Strykar Nope, see https://aur.archlinux.org/packages/wine-ge-custom#comment-831304
You can grab compiled packages from https://github.com/loathingKernel/PKGBUILDs/releases/tag/packages
loathingkernel commented on 2021-10-15 10:01 (UTC) (edited on 2021-10-15 10:04 (UTC) by loathingkernel)
@thaewrapt, I see, you might be correct. The prebuilt package is not a good candidate for packaging for a couple of reasons. First of all, it is built using Lutris's runtime, and as such inherits the same issues as Proton, namely it is at its best when running inside that runtime. Also, although I might be wrong here, I haven't found any mention of Lutris being able to use a system-wide installation directory in the same way Steam can. For these reasons, I believe that packaging those binaries is pointless and they should be managed by Lutris itself.