Package Details: wine-valve 5:8.0.5-1

Git Clone URL: https://aur.archlinux.org/wine-valve.git (read-only, click to copy)
Package Base: wine-valve
Description: A compatibility layer for running Windows programs (Valve version)
Upstream URL: https://github.com/ValveSoftware/wine.git
Licenses: LGPL
Conflicts: bin32-wine, wine, wine-staging, wine-staging-git, wine-wow64
Provides: bin32-wine, wine, wine-valve, wine-wow64
Replaces: bin32-wine
Submitter: heavysink
Maintainer: heavysink (lilac)
Last Packager: lilac
Votes: 12
Popularity: 0.43
First Submitted: 2020-06-12 13:41 (UTC)
Last Updated: 2023-12-19 21:13 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

mmmaisel commented on 2024-09-20 16:10 (UTC)

The "-Wl" gcc issue is caused by an incomplete string substitution. To fix this, in the prepare() function replace the line export LDFLAGS="${LDFLAGS/,-z,now/}" with export LDFLAGS="${LDFLAGS/-Wl,-z,now/}".

Also when building newer wine-valve versions like 9.0, some header files have to be generated with a script. To do so, in the prepare function add ./tools/make_specfiles directly after ./dlls/winevulkan/make_vulkan.

TipsyTheCat commented on 2024-08-08 01:30 (UTC)

When installing, fails at:

checking whether the C compiler works... no
configure: error: in '/run/media/tipsy/HDD/pamac-AUR-build-dir/wine-valve/src/wine-valve-64-build':
configure: error: C compiler cannot create executables
See 'config.log' for more details
==> ERROR: A failure occurred in build().
    Aborting...

Taking a peek in config.log:

checking whether the C compiler works
configure:5290: gcc -march=x86-64 -mtune=generic -O2 -pipe  -fexceptions         -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection         -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffat-lto-objects  -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl          -Wl,-z,pack-relative-relocs conftest.c  >&5
gcc: error: unrecognized command-line option '-Wl'; did you mean '-W'?
configure:5294: $? = 1
configure:5335: result: no

I'm not sure if wine is simply being built wrong or if this is an issue i need to report to valves wine repo? it seems like the -Wl flag is being used incorrectly, causing gcc to not recognize the flag. Notably though, there is alot of whitespace after it as well as in other places in the command to call gcc. I'm not sure what this could mean though... I also tried with _pkgver set to 9.0-2 for the latest version, but got the exact same problem.

And that's about the end of what I know. I'm kinda out of my depth a bit here, just trying to install wine with valves game specific tweaks as my system wine.

FoxMaccloud commented on 2023-04-12 15:09 (UTC)

Error attempting to update wine-valve with yay.

../wine-proton-wine-7.0-6e/tools/install-sh -m 644  tools/wmc/wmc.man /home/foxmaccloud/.cache/yay/wine-valve/pkg/wine-valve/usr/share/man/man1/wmc.1
STRIPPROG="strip" ../wine-proton-wine-7.0-6e/tools/install-sh  tools/wmc/wmc /home/foxmaccloud/.cache/yay/wine-valve/pkg/wine-valve/usr/bin/wmc
../wine-proton-wine-7.0-6e/tools/install-sh -m 644  tools/wrc/wrc.man /home/foxmaccloud/.cache/yay/wine-valve/pkg/wine-valve/usr/share/man/man1/wrc.1
STRIPPROG="strip" ../wine-proton-wine-7.0-6e/tools/install-sh  tools/wrc/wrc /home/foxmaccloud/.cache/yay/wine-valve/pkg/wine-valve/usr/bin/wrc
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: wine-valve-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
wine-valve - exit status 4

xiretza commented on 2023-02-26 09:07 (UTC)

What's the reason for the options=('!debug' 'strip') in the latest commit?

NY152 commented on 2023-02-24 22:58 (UTC)

Same error as mynis01 ...

mynis01 commented on 2023-02-14 19:38 (UTC)

I had issues building this package with yay ever since the update to 3:7.0.6-1 in December. Today I had the idea to start to install wine-stable and keep the dependencies and then cancel the install of wine-stable. I was able to build wine-valve without issues afterwards. So there might be a missing dependency here. The error I was getting at the end of the build attempt was this:

error: undefined symbol: _D3DKMTEnumAdapters2@4

jsimon0 commented on 2022-02-22 03:12 (UTC)

@mmmaisel Indeed it does. I was hoping the EAC support would get a playable Division 2 but that seems to require some work by Ubisoft or possibly some messing about by me.

Also, is your handle a Marvelous Mrs Maisel reference?

mmmaisel commented on 2022-02-21 19:07 (UTC)

@jsimon0 I played some games with it so it works.

1 2 3 4 5 6 Next › Last »