Package Details: wine-wl-git 7.10.r14025.gdb5fb59a1ca-1

Git Clone URL: https://aur.archlinux.org/wine-wl-git.git (read-only, click to copy)
Package Base: wine-wl-git
Description: A compatibility layer for running Windows programs (wayland version from gitlab.collabora.com/alf/wine/ wayland branch)
Upstream URL: http://www.winehq.com
Keywords: wayland wine
Licenses: LGPL
Conflicts: wine, wine64
Provides: wine, wine64
Submitter: sem.z
Maintainer: sem.z
Last Packager: sem.z
Votes: 6
Popularity: 1.54
First Submitted: 2021-04-24 17:43 (UTC)
Last Updated: 2022-06-11 19:31 (UTC)

Required by (306)

Sources (3)

Pinned Comments

skylize commented on 2022-06-14 00:05 (UTC) (edited on 2022-06-14 00:09 (UTC) by skylize)

Also ran into the same problem as @estebiu and @Kyuunex, of "failed to set dynamic section sizes". Solved by adding MAKEFLAGS=-j1 to the PKGBUILD (overriding my settings in makepkg.conf for parallel jobs). Glacially slow to build, but actually completes.

This should probably be added to the maintained PKGBUILD. (As the Arch Wiki suggests is somewhate common practice. https://wiki.archlinux.org/title/Makepkg#Improving_compile_times)

Latest Comments

Sethox commented on 2022-06-21 05:49 (UTC)

Just so you guys know, I've been able to compile with more jobs than 1 for a while now. No errors or disruptions.

sem.z commented on 2022-06-14 07:34 (UTC)

@skylize, thank you for investigation of this problem. This change makes build time very slow, so I wouldn't make it, because I don't know how common is this problem and if this change worth it. I can build it, chaotic aur builds it, and, probably many more people successfully build it, it's really hard to say, there is only 3 people wrote about this problem. I would pin your comment, so if someone encounters this issue they would set this flag.

skylize commented on 2022-06-14 00:05 (UTC) (edited on 2022-06-14 00:09 (UTC) by skylize)

Also ran into the same problem as @estebiu and @Kyuunex, of "failed to set dynamic section sizes". Solved by adding MAKEFLAGS=-j1 to the PKGBUILD (overriding my settings in makepkg.conf for parallel jobs). Glacially slow to build, but actually completes.

This should probably be added to the maintained PKGBUILD. (As the Arch Wiki suggests is somewhate common practice. https://wiki.archlinux.org/title/Makepkg#Improving_compile_times)

sem.z commented on 2022-06-11 19:33 (UTC)

I updated package version calculation, now it takes version from VERSION file, not from tags. Sorry for the inconvenience.

sem.z commented on 2022-06-11 17:32 (UTC)

@estebiu, there is Chaotic AUR repository, it builds this package, so you can install it from there if you would not fix this issue.

estebiu commented on 2022-06-09 21:16 (UTC)

Build fails with this error:

/sbin/ld: dlls/openal32/openal.o: direct GOT relocation R_386_GOT32X against `alcCreateContext' without base register can not be used when making a shared object
/sbin/ld: failed to set dynamic section sizes: Success
collect2: error: ld returned 1 exit status
winegcc: /sbin/gcc failed
make: *** [Makefile:127485: dlls/openal32/openal32.dll.so] Error 2
==> ERROR: A failure occurred in build().
Anyone knows how to fix it?

Sethox commented on 2022-06-06 20:11 (UTC)

@dr460nf1r3 The git repository left the Git tag at the version they forked it and haven't updated the tag since then.

What you see is the git tag. But the version is on the version file in the repository. I myself tend to read the activity tab on the git repository, thus I follow the updates and such. But to answer your question, it's a newer 7.0 version and not the 6.0 branch.

dr460nf1r3 commented on 2022-06-06 12:04 (UTC)

I'm confused, the PKGBUILD seems to build from the correct branch but still shows the 6.0r1 tag when running wine --version. Is this the actual version 6.0rc1 or is this version also set due to the latest tag?

Sethox commented on 2022-02-21 09:18 (UTC) (edited on 2022-02-21 12:36 (UTC) by Sethox)

@sem.z sorry, there is no way (that I know of) to change the version/tag. I just commented on it not as a critique but as information provided (of what the Wine version provides).

Edit: I looked it up and you can do a 'printf <insert version name here>' under the pkgver() in the PKGBUILD. Hacky thing to do... but eh..

sem.z commented on 2022-01-31 07:13 (UTC)

@Sethox, yes, you are right, thank you for your observation. How do you think I should change version generation? Current version uses latest tag, which is 6.0 rc1.

Sethox commented on 2022-01-28 16:12 (UTC)

It's interesting to know that the Wayland branch now provides 7.0 (not RC) wine version now. I tend to look every now and then of the activity to see the life and progress (and to compile and test).

WFCody commented on 2021-12-13 04:09 (UTC)

The wayland-staging-wip branch seems to be older than the wayland and the wayland-wip branches:

https://gitlab.collabora.com/alf/wine/-/branches

HanFox commented on 2021-12-12 15:40 (UTC)

I got the same error as IncredibleLaser (albeit on a cleanly installed system, not a chroot).

wayland-protocols should be in the makedepends.

IncredibleLaser commented on 2021-10-20 14:31 (UTC) (edited on 2021-10-20 14:33 (UTC) by IncredibleLaser)

Trying to build this in a clean chroot results in the following error during configure:

configure: error: Wayland 64-bit development files not found or not new enough, the Wayland driver won't be supported.
This is an error since --with-wayland was requested.

From a first guess, the package requires wayland and lib32-wayland

lavilao commented on 2021-10-15 22:51 (UTC)

ops sorry about previous comment, I jus found the reason lib32-libxkbcommon was not installed xD. But now I have another issue, the window renders and I know its wayland because of the windows xp theme but keyboard input is not detected, I can click and the window reacts to it but the keyboard is a fat no. any ideas?

lavilao commented on 2021-10-15 22:42 (UTC)

setting the DISPLAY= throws this error "Error initializing SDL: No displays available" setting it to DISPLAY=:0 fixes it but its on xwayland so... its useless any clue why? I am using Sway btw

ArchXUser commented on 2021-10-06 12:43 (UTC)

Set DISPLAY env to nothing, for example, you can run winecfg so DISPLAY= winecfg. Also, you need to set properly WAYLAND_DISPLAY, for example, WAYLAND_DISPLAY=wayland-1.

burrhole commented on 2021-09-23 10:23 (UTC)

Is there a flag or environment variable that needs to be set to run programs via Wayland with this build? After installing this package and running any program with Wine, it's still running in XWayland on my system.

juxuanu commented on 2021-09-16 08:26 (UTC)

dxvk-mingw-git requires wine>=4.0rc1 so when that package is installed, this one fails to install (replacing, for example, wine).

What should change in this PKGBUILD's provides? Or is this dxvk-mingw-git fault?

PedroHLC commented on 2021-09-14 23:41 (UTC)

looks like the most recent branch now is wayland-staging-wip

Kyuunex commented on 2021-08-12 14:41 (UTC)

although if i do switch the branch to wayland and remove that symlink, it does build

Kyuunex commented on 2021-08-11 12:48 (UTC)

build fails with

/sbin/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: /sbin/gcc failed
make: *** [Makefile:12545: dlls/capi2032/capi2032.dll.so] Error 2
make: *** Waiting for unfinished jobs....
==> ERROR: A failure occurred in build().
    Aborting...
error making: wine-wl-git