Package Details: wine-staging-git 7.3.r5.ga79a08a6-1

Git Clone URL: https://aur.archlinux.org/wine-staging-git.git (read-only, click to copy)
Package Base: wine-staging-git
Description: A compatibility layer for running Windows programs (staging branch, git version)
Upstream URL: https://www.wine-staging.com/
Keywords: staging windows wine
Licenses: LGPL
Conflicts: wine, wine-wow64
Provides: wine, wine-staging, wine-wow64
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 18
Popularity: 0.136302
First Submitted: 2016-03-27 06:19 (UTC)
Last Updated: 2022-03-08 17:15 (UTC)

Required by (313)

Sources (4)

Latest Comments

linuxham commented on 2021-07-03 21:49 (UTC)

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

linuxham commented on 2021-06-28 14:17 (UTC)

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.

dbermond commented on 2021-06-27 03:35 (UTC)

@linuxham You need to enable the multilib repository.

linuxham commented on 2021-06-27 00:15 (UTC)

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.

dbermond commented on 2021-05-11 13:48 (UTC)

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

cysp74 commented on 2021-05-11 11:03 (UTC)

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
 }

cysp74 commented on 2021-04-29 11:39 (UTC)

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

dbermond commented on 2021-02-09 19:08 (UTC)

@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.

katt commented on 2021-02-08 23:59 (UTC)

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

dbermond commented on 2020-03-07 16:12 (UTC)

@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.

alcarinque commented on 2020-03-06 14:50 (UTC) (edited on 2020-03-06 14:50 (UTC) by alcarinque)

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

dbermond commented on 2019-12-06 20:00 (UTC)

@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.

hugegameartgd commented on 2019-12-04 19:43 (UTC) (edited on 2019-12-04 19:43 (UTC) by hugegameartgd)

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

some53 commented on 2019-12-04 03:23 (UTC)

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

dbermond commented on 2019-12-03 15:52 (UTC)

@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.

some53 commented on 2019-12-03 09:47 (UTC)

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...

dbermond commented on 2019-11-20 21:51 (UTC)

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

hugegameartgd commented on 2019-11-17 16:55 (UTC)

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

dbermond commented on 2019-05-18 18:29 (UTC)

@LinuxLoverForeve Package is building fine for me.

LinuxLoverForeve commented on 2019-05-16 20:48 (UTC)

This package fails to compile.

dbermond commented on 2019-04-19 17:05 (UTC)

@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

electricprism commented on 2019-04-14 21:49 (UTC)

3.18 is legacy it should be updated or dropped.

dbermond commented on 2018-12-11 13:51 (UTC)

@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.

C0rn3j commented on 2018-12-11 10:05 (UTC)

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

dbermond commented on 2018-10-11 21:41 (UTC)

@SilverSynch Thank you for reporting this. Package updated.

SilverSynch commented on 2018-10-11 16:58 (UTC)

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

dbermond commented on 2018-03-04 20:15 (UTC)

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.

Shatur commented on 2018-03-04 10:25 (UTC)

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

dbermond commented on 2018-02-24 13:27 (UTC)

@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

ahjolinna commented on 2018-02-20 09:11 (UTC)

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)

dbermond commented on 2018-02-18 17:09 (UTC)

@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.

ahjolinna commented on 2018-02-18 00:11 (UTC)

@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)

dbermond commented on 2017-10-03 00:31 (UTC)

@ahjolinna Yes, it is now building and working as usual after the rebase commits. Thank you for the report.

ahjolinna commented on 2017-10-02 23:44 (UTC)

everything works now...(it's A LIVE!! it's A LIVE!!!)...now back to playing SW:TOR asp (it requires staging to work)

dbermond commented on 2017-09-28 16:32 (UTC)

@ahjolinna That's normal and expected. In my previous comment I have already stated that wine-staging-git can take a little longer to get the fix, since it needs an upstream rebase commit. And this rebase commit not happened yet at the time of this writing.

ahjolinna commented on 2017-09-28 16:21 (UTC) (edited on 2017-09-28 16:58 (UTC) by ahjolinna)

wine-git builds now with ft2.8.1 but wine-staging(-git) wont..yet

dbermond commented on 2017-09-24 15:59 (UTC)

@Cork and @ahjolinna I can reproduce the issue. Thank you for reporting this. The proposed patch from wine bug #43715 does not fix the building issue. Package still does not build after applying the mentioned patch. Since this is an upstream problem, there is nothing we can do here on the packaging side. The bug reports were marked as blocker ones and we should wait for an upstream fix. Since we are using wine-staging, things can take a little longer because we may need an upstream rebase commit, and sometimes this happens only near the next release. The only "solution" currently available is to downgrade freetype, as stated by a wine developer in the duplicated wine bug #43762 (comment #2).

ahjolinna commented on 2017-09-24 12:13 (UTC) (edited on 2017-09-24 12:17 (UTC) by ahjolinna)

wine (at least) doesn't work with freetype 2.8.1 https://bugs.winehq.org/show_bug.cgi?id=43715 https://bugs.winehq.org/show_bug.cgi?id=43716 (there is a patch)

Cork commented on 2017-09-22 21:21 (UTC)

Compiling gives me make[1]: Entering directory '/var/build/wine-staging-git/src/wine-staging-git-64-build/fonts' ../tools/sfnt2fon/sfnt2fon -o coue1255.fon ../../wine-git/fonts/courier.ttf -d 128 13,1255,8 Error: Cannot open face ../../wine-git/fonts/courier.ttf make[1]: *** [Makefile:182: coue1255.fon] Error 1 but src/wine-git/fonts contains the font.

dbermond commented on 2017-09-11 16:24 (UTC)

@ccxex29 Hi. Sorry, but I cannot reproduce your issue. Package is building fine for me. What are you using to build? AUR helper or makepkg? And what is the command?

ccxex29 commented on 2017-09-11 15:55 (UTC)

Hello! I got this error by updating : Option --inode is useless without option --long. configure: error: working directory cannot be determined ==> ERROR: A failure occurred in build().

dbermond commented on 2017-06-29 18:51 (UTC)

@Narthorn Thank you for reporting this. I'm glad that pkgver() is still giving the correct version, so the package itself is not affected. I'll be fixing it as soon as I can.

Narthorn commented on 2017-06-28 07:09 (UTC) (edited on 2017-06-28 07:13 (UTC) by Narthorn)

pkgver() fails to translate the latest-release git tag to 2.11, giving 2.9 instead. This can be fixed by using sort -Vr, or directly git tag --sort -v:refname.

dbermond commented on 2017-01-14 22:11 (UTC)

@Anthony25 Thank you for the report. It's building fine for me again too so probably it was an upstream issue.

Anthony25 commented on 2017-01-14 16:35 (UTC)

It's building without problem now, thanks again!

Anthony25 commented on 2017-01-11 12:41 (UTC)

@Bermond: Ok, thanks a lot for your answer, I didn't know if it was an upstream issue or a missing dependency to do the build. So I'll wait!

dbermond commented on 2017-01-11 00:17 (UTC) (edited on 2017-01-11 00:27 (UTC) by dbermond)

@Anthony25 I'm also getting this same error in latest builds during the 64-bit compilation phase. It seems to be not specific for this package since this same problem is happening to me with wine-git AUR package as well. Also, as you can see, wine-staging x86_64 repository package was not updated to 2.0 rc4 while i686 was updated, hinting that maybe some problem may have occurred in 64-bit builds for the latest version. So this seems to be an upstream problem and maybe 64-bit specific. Let's wait some days and see if it is fixed by upstream since 2.0 release is getting closer. If you have a clue or any other view please share your thoughts.

dbermond commented on 2017-01-10 23:35 (UTC)

@ProfessorKaos64 Thanks for appreciating :)

Anthony25 commented on 2017-01-10 18:29 (UTC)

Hello, Since a few days, in a clean-chroot or not, I get this error while compiling: ``` macro.lex.yy.o: In function `yylex': macro.lex.yy.c:(.text+0xf3d): undefined reference to `yywrap' ```

ProfessorKaos64 commented on 2016-12-17 22:59 (UTC)

Thanks for putting this up

dbermond commented on 2016-04-13 21:00 (UTC)

@Xylemon Done.

Xylemon commented on 2016-04-08 18:11 (UTC) (edited on 2016-04-08 18:14 (UTC) by Xylemon)

Could you add OSS to the optional deps as well?