| 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) |
# Make a backup of my makepkg.conf
sudo mv /etc/makepkg.conf /etc/makepkg.conf.back
# Reinstall pacman to recover original makepkg.conf
sudo pacman -S pacman
# Compare files
diff /etc/makepkg.conf /etc/makepkg.conf.back
Results in
< #MAKEFLAGS="-j2"
---
> MAKEFLAGS="-j20"
Relaunched makepkg -is but exactly the same output. What am I doing wrong ?
@xiota, hmmm this is strange, to my knowledge the only change I made was to uncomment this line to allow parallel compilation:
MAKEFLAGS="-j20"
I will restore the original file from the package and see what happens.
@gdebure The -fuse-ld=lld in your output indicates makepkg.conf has been modified. This package builds successfully in a clean chroot.
I get the following message when installing on a fresh archlinux install:
...
checking whether the compiler supports -Wl,--export-dynamic... yes
checking whether the compiler supports -static-pie... yes
checking for x86_64-w64-mingw32-gcc... x86_64-w64-mingw32-gcc
checking whether x86_64-w64-mingw32-gcc works... yes
checking whether x86_64-w64-mingw32-gcc supports -target x86_64-w64-mingw32 -fuse-ld=lld --no-default-config... no
checking whether x86_64-w64-mingw32-gcc supports -target x86_64-w64-mingw32 -fuse-ld=lld ... no
checking for x86_64-w64-mingw32-gcc option to enable C99 features... unsupported
configure: error: x86_64 PE cross-compiler supporting C99 not found.
This is an error since --enable-archs=x86_64 was requested.
It is not clear to me what I should install prior to installing wine-wow64. Should something more be listed as build dependencies ?
@kby, you are doing it wrong, read https://wiki.archlinux.org/title/Makepkg#Improving_build_times
It took me 4m 38s on Ryzen 7700X with all 16 threads utilized and building on tmpfs ramdisk.
Any tips to decrease compilation time? I've tried -j8 for the make call in build(), but that didn't make it any faster. Right now, the entire process takes about an hour for me.
@yan12125 I've moved sane and samba to makedep/optdep.
Dear Daniele, Can you please check wine64 issue: https://github.com/Winetricks/winetricks/pull/2191
On my machine, samba also brings smbclient. Those extra dependencies use 20% extra space compared to wine-wow64 (just ignore the giant multilib/wine).
Not a big deal, anyway.
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/winedoes 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.
tiziodcaio commented on 2023-09-11 14:58 (UTC)
Added wine-staging-wow64, the wine-wow64 package with staging patches!