Arch Linux User Repository

mine is solved, I didn't uncomment #multilib, just the line below

Thanks, I enabled multilib but still had multiple unmet dependancies

==> Installing missing dependencies... error: target not found: lib32-attr error: target not found: lib32-fontconfig error: target not found: lib32-lcms2 error: target not found: lib32-libxml2 error: target not found: lib32-libxcursor error: target not found: lib32-libxrandr error: target not found: lib32-libxdamage error: target not found: lib32-libxi error: target not found: lib32-gettext error: target not found: lib32-freetype2 error: target not found: lib32-glu error: target not found: lib32-libsm error: target not found: lib32-libpcap error: target not found: lib32-faudio ==> ERROR: 'pacman' failed to install missing dependencies.

@linuxham You need to enable the multilib repository.

when I try running makepkg -si, I get a list of unmet dependencies.

==> Installing missing dependencies... error: target not found: lib32-attr error: target not found: lib32-fontconfig error: target not found: lib32-lcms2 error: target not found: lib32-libxml2 error: target not found: lib32-libxcursor error: target not found: lib32-libxrandr error: target not found: lib32-libxdamage error: target not found: lib32-libxi error: target not found: lib32-gettext error: target not found: lib32-freetype2 error: target not found: lib32-glu error: target not found: lib32-libsm error: target not found: lib32-libpcap error: target not found: lib32-faudio ==> ERROR: 'pacman' failed to install missing dependencies. ==> Missing dependencies: -> lib32-attr -> lib32-fontconfig -> lib32-lcms2 -> lib32-libxml2 -> lib32-libxcursor -> lib32-libxrandr -> lib32-libxdamage -> lib32-libxi -> lib32-gettext -> lib32-freetype2 -> lib32-glu -> lib32-libsm -> lib32-gcc-libs -> lib32-libpcap -> faudio -> lib32-faudio ==> Checking buildtime dependencies... ==> Installing missing dependencies... error: target not found: lib32-giflib error: target not found: lib32-libpng error: target not found: lib32-gnutls error: target not found: lib32-libxinerama error: target not found: lib32-libxcomposite error: target not found: lib32-libxmu error: target not found: lib32-libxxf86vm error: target not found: lib32-libldap error: target not found: lib32-mpg123 error: target not found: lib32-openal error: target not found: lib32-v4l-utils error: target not found: lib32-alsa-lib error: target not found: lib32-libxcomposite error: target not found: lib32-mesa error: target not found: lib32-libgl error: target not found: lib32-opencl-icd-loader error: target not found: lib32-libxslt error: target not found: lib32-libpulse error: target not found: lib32-libva error: target not found: lib32-gtk3 error: target not found: lib32-gst-plugins-base-libs error: target not found: lib32-vulkan-icd-loader error: target not found: lib32-sdl2 error: target not found: lib32-vkd3d error: target not found: lib32-libcups ==> ERROR: 'pacman' failed to install missing dependencies. ==> Missing dependencies: -> lib32-giflib -> lib32-libpng -> lib32-gnutls -> lib32-libxinerama -> lib32-libxcomposite -> lib32-libxmu -> lib32-libxxf86vm -> lib32-libldap -> lib32-mpg123 -> lib32-openal -> lib32-v4l-utils -> lib32-alsa-lib -> lib32-libxcomposite -> lib32-mesa -> lib32-libgl -> opencl-icd-loader -> lib32-opencl-icd-loader -> lib32-libxslt -> lib32-libpulse -> lib32-libva -> lib32-gtk3 -> lib32-gst-plugins-base-libs -> lib32-vulkan-icd-loader -> lib32-sdl2 -> vkd3d -> lib32-vkd3d -> lib32-libcups -> sane -> libgphoto2 -> samba -> opencl-headers -> vulkan-headers ==> ERROR: Could not resolve all dependencies.

@cysp74 Package updated to match the latest upstream changes. Building fine now.

Solution is:

diff --git a/PKGBUILD b/PKGBUILD
old mode 100644
new mode 100755
index 6b7a7ec..5016526
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Daniel Bermond <dbermond@archlinux.org>

 pkgname=wine-staging-git
-pkgver=6.5.r1.g2e42e7d9
+pkgver=6.8.r3.g7f18df46
 pkgrel=1
 pkgdesc='A compatibility layer for running Windows programs (staging branch, git version)'
 arch=('x86_64')
@@ -194,6 +194,6 @@ package() {
     install -D -m644 "${srcdir}/wine-binfmt.conf" "${pkgdir}/usr/lib/binfmt.d/wine.conf"

     # strip native PE libraries
-    i686-w64-mingw32-strip --strip-unneeded "${pkgdir}/usr/lib32/wine"/*.dll
-    "${CARCH}-w64-mingw32-strip" --strip-unneeded "${pkgdir}/usr/lib/wine"/*.dll
+    i686-w64-mingw32-strip --strip-unneeded "${pkgdir}/usr/lib32/wine"/*/*.dll
+    "${CARCH}-w64-mingw32-strip" --strip-unneeded "${pkgdir}/usr/lib/wine"/*/*.dll
 }

For couple of days building has been failing to PKGBUILD tries to strip dll, but directory structure is changed - looks like.

PKGBUILD

# strip native PE libraries
i686-w64-mingw32-strip --strip-unneeded "${pkgdir}/usr/lib32/wine"/*.dll
"${CARCH}-w64-mingw32-strip" --strip-unneeded "${pkgdir}/usr/lib/wine"/*.dll

Throws:

i686-w64-mingw32-strip: '/xxx/xxx/wine-staging-git/pkg/wine-staging-git/usr/lib32/wine/*.dll': No such file

Due to no dlls can be found at target level, only two directories:

i386-unix  i386-windows

@katt Maybe this case it may be useful to add the version to wine in provides. Using $pkgver would not be correct, since wine and wine-staging have each one their own git repository, so pkgver is different between them. I've used the wine point release, although this is non-optimal.

Could this provide wine=${pkgver}? Running into this:

:: wine-staging-git and wine-git are in conflict (wine). Remove wine-git? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing wine-git breaks dependency 'wine>=4.0rc1' required by dxvk-mingw

@alcarinque I'm also getting this error. Apparently, this is being caused by the recent upstream commit 2fc5c88 that adds the xactengine-initial patchset.

This should be reported upstream.

I'll temporarily disable this recently introduced patchset so that the package can be built.

I have this error when building. The x3daudio1_7 directory builds fine.

make[1]: Entering directory '/home/alcarinque/wine-build/wine-staging-git/src/wine-staging-git-64-build/dlls/xaudio2_7/tests'

../../../tools/winegcc/winegcc -o xaudio2_7_test-stripped.exe.so --wine-objdir ../../.. -m64 -fPIC -fasynchronous-unwind-tables \ -s -Wb,-F,xaudio2_7_test.exe -mno-cygwin xact.o xaudio2.o testlist.o rsrc.res -lole32 \ -lx3daudio1_7 -Wl,-O1,--sort-common,--as-needed,-z,relro

/usr/bin/ld: cannot find -lx3daudio1_7

@some53 Sorry, but Manjaro is not supported.

@hugegameartgd Maybe the cause was some outdated VCS (-git) package. When you use VCS packages you are for your own and must track everything carefully. Note that you also need the multilib-devel group.

@dbermond I reinstalled base-devel with pacman (testing repo) which replaced some *-git packages and now it's compiling for me too.

@dbermond Thank you for your help. I was using pamac package manager in Manjaro. Anyway it worked after refreshing database.

@some53 Package is building fine. I have no problems.

I see that you're using an AUR helper, and this is not supported. Please use makepkg.

Hello, The latest version is not building, I get,

../../../wine/dlls/directmanipulation/directmanipulation.c:29:10: fatal error: directmanipulation.h: No such file or directory 29 | #include "directmanipulation.h" | ^~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make[1]: *** [Makefile:181: directmanipulation.o] Error 1 make[1]: Leaving directory '/var/tmp/pamac-build-sobuj/wine-staging-git/src/wine-staging-git-64-build/dlls/directmanipulation' make: *** [Makefile:8779: dlls/directmanipulation] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

@hugegameartgd Package is building fine. Try to build it in a clean chroot.

I get

checking for msgfmt... msgfmt
../wine/configure: line 7521: syntax error near unexpected token `newline'
../wine/configure: line 7521: `    '''

when trying to compile wine-staging-git 4.20.r0.g356f2282+wine.4.20.r0.g60626d0df8-1

@LinuxLoverForeve Package is building fine for me.

This package fails to compile.

@electricprism The version will be automatically updated by the pkgver() function when you run makepkg. No need to update the major version at each upstream release. This is how VCS packages work. See the Wiki:

https://wiki.archlinux.org/index.php/PKGBUILD#pkgver

https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function

3.18 is legacy it should be updated or dropped.

@C0rn3j This can be a lot of things on your system or even on the machine. Try to build in a clean chroot and see if it works.

https://haste.rys.pw/raw/acibawakus I can't build this package on a system with Ryzen 2400G, it works on a Ryzen 1700 box. Compressed compilation folder (0.5GB) - https://cloud2.rys.pw/s/oNyL9DQc5TFN76d

It seems to fail on random things each run.

during RTL pass: final ../../../wine-git/dlls/wined3d/arb_program_shader.c: In function ‘shader_arb_select’: ../../../wine-git/dlls/wined3d/arb_program_shader.c:4688:1: internal compiler error: Segmentation fault

@SilverSynch Thank you for reporting this. Package updated.

The Freetype Harmony fix has been merged in Wine. It cannot remain in the package as the patch fails to apply.

https://source.winehq.org/git/wine.git/commit/66e446c5ec5c7f4f072358712151d75305dfbd49

Important notice:

Upstream wine-staging hosted at 'https://github.com/wine-compholio/wine-staging/' is no more maintained. A community fork is now maintained at 'https://github.com/wine-staging/wine-staging/'.

As a result, the source repository of this package has changed. If you have a copy of the old source repository on disk and want to upgrade the package, please follow this step: before running makepkg, delete the directory wine-staging-git from the location where the PKGBUILD file is placed. New users building the package for the first time does not need to do anything.

Wine Staging 3.3 released: https://github.com/wine-staging/wine-staging/releases I suggest to change link in PKGBUILD to this fork.

@ahjolinna As far as I can tell, the new wine-staging will not be maintained by the Lutris team.

It will be maintained by Alistair at the following repository (which is not from Lutris): https://github.com/wine-staging/wine-staging/

The Lutris post on Twitter that you shared is just some news about the new wine-staging repository. It does not mean that they are now maintaining it. It seems that the people who commented there do not get the point.

See here: https://www.winehq.org/pipermail/wine-devel/2018-February/123080.html

it seems the Lutris people are going to maintain the fork https://twitter.com/LutrisGaming/status/965329572873949184 ..but I'm not sure but could be that they are not going to release any new patches, only existant patches will be refreshed for each version of Wine...which is fine (for now)

@ahjolinna Yes, I'm aware of all this situation and the surrounding discussions. Although the wine-staging news page mention the fork made by Alistair (github user @alesliehughes), there is currently no official word from the wine team of what will become wine-staging, and there is no guarantee that this fork will be the new wine-staging post-3.0. So I think that it's a bit early to change things here, and that it will be more prudent to wait a little longer to see how this transition will be adopted and received by the mainstream people. Besides, the current wine-staging 2.21 is building and working fine. Thank you for the interest. Let's see how this will develop in the (hopefully) near future.

@dbermond: have you seen this? https://www.winehq.org/pipermail/wine-devel/2018-February/122848.html

maybe move/change to the fork? (which they recommend)