Package Details: wine-wow64 9.22-1

Git Clone URL: https://aur.archlinux.org/wine-wow64.git (read-only, click to copy)
Package Base: wine-wow64
Description: A compatibility layer for running Windows programs
Upstream URL: https://www.winehq.org
Keywords: wine winehq wow64 x64
Licenses: LGPL-2.1-or-later
Conflicts: wine
Provides: wine
Submitter: tiziodcaio
Maintainer: tiziodcaio (xiota)
Last Packager: xiota
Votes: 38
Popularity: 1.43
First Submitted: 2023-05-06 18:16 (UTC)
Last Updated: 2024-11-23 18:38 (UTC)

Pinned Comments

xiota commented on 2024-05-22 12:10 (UTC) (edited on 2024-05-23 05:13 (UTC) by xiota)

This package is still relevant because multilib/wine does not have wow64 mode enabled and/or has not dropped lib32 depends.

Hanabishi commented on 2024-05-22 11:55 (UTC) (edited on 2024-05-22 12:01 (UTC) by Hanabishi)

@dreieck, https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0#wow64

TLDR: with new WoW64 mode, you can run 32-bit Windows apps on pure 64-bit Linux system, i.e. without multilib/lib32-* dependencies installed.

xiota commented on 2024-01-18 02:30 (UTC)

Wayland support requires setting a registry variable. See Wine 9.0 Changelog.

wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d x11,wayland

tiziodcaio commented on 2023-09-11 14:58 (UTC)

Added wine-staging-wow64, the wine-wow64 package with staging patches!

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Hanabishi commented on 2024-05-11 00:21 (UTC)

Probably will be good for this package to also pick up a recent optimization.

xiota commented on 2024-04-23 06:15 (UTC)

@gdebure Something is changing the build settings on your computer. Could be almost anything. Would be interested to know if you ever find it.

gdebure commented on 2024-04-23 05:27 (UTC) (edited on 2024-04-23 05:28 (UTC) by gdebure)

Indeed, it does build in a clean chroot... I can see a few diffs between the system's makepkg.conf and the chroot one, but not sure they are relevant:

diff /etc/makepkg.conf /var/lib/archbuild/extra-x86_64/root/etc/makepkg.conf

44,46c44,45
<         -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
<         -fstack-clash-protection -fcf-protection \
<         -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
---
>         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security \
>         -fstack-clash-protection -fcf-protection"
51c50
< RUSTFLAGS="-Cforce-frame-pointers=yes"
---
> RUSTFLAGS=""
86c85
< # Makepkg defaults: OPTIONS=(!strip docs libtool staticlibs emptydirs !zipman !purge !debug !lto !autodeps)
---
> # Makepkg defaults: OPTIONS=(!strip docs libtool staticlibs emptydirs !zipman !purge !debug !lto)
98d96
< #-- autodeps:   Automatically add depends/provides
118,119d115
< #-- Prefix and directories for library autodeps
< LIB_DIRS=('lib:usr/lib' 'lib32:usr/lib32')

gdebure commented on 2024-04-23 04:38 (UTC) (edited on 2024-04-23 04:39 (UTC) by gdebure)

Well, it looks like the original makepkg.conf from pacman 6.1 uses these LDFLAGS:

LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now
         -Wl,-z,pack-relative-relocs"

(source : https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/blob/6.1/makepkg.conf?ref_type=heads)

I will try building in a clean chroot.

xiota commented on 2024-04-22 22:29 (UTC) (edited on 2024-04-22 22:30 (UTC) by xiota)

Why is it trying to use lld? Do you have LDFLAGS and other variables set somewhere else? Try building in clean chroot.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »