Search Criteria
Package Details: wine-git 7.3.r297.g99ef287bb72-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/wine-git.git (read-only, click to copy) |
---|---|
Package Base: | wine-git |
Description: | A compatibility layer for running Windows programs (git version) |
Upstream URL: | https://www.winehq.org/ |
Keywords: | windows wine |
Licenses: | LGPL |
Conflicts: | bin32-wine, wine, wine-wow64 |
Provides: | bin32-wine, wine, wine-wow64 |
Replaces: | bin32-wine |
Submitter: | None |
Maintainer: | dbermond |
Last Packager: | dbermond |
Votes: | 86 |
Popularity: | 0.107517 |
First Submitted: | 2007-07-18 16:01 (UTC) |
Last Updated: | 2022-03-08 17:15 (UTC) |
Dependencies (130)
- desktop-file-utils (desktop-file-utils-git)
- faudio (faudio-git)
- fontconfig (fontconfig-srb, fontconfig-minimal-git, fontconfig-git, fontconfig-ubuntu)
- freetype2 (freetype2-minimal-git, freetype2-ttmetrics, freetype2-v35, freetype2-git, freetype2-ultimate5, freetype2-infinality-remix)
- gcc-libs (fastgcc, gcc-libs-git, gccrs-libs-git)
- gettext (gettext-git)
- glu (glu-git)
- lcms2 (lcms2-git)
- lib32-faudio (lib32-faudio-git)
- lib32-fontconfig (lib32-fontconfig-git)
- lib32-freetype2 (lib32-freetype2-old-hinting, lib32-freetype2-infinality-ultimate, lib32-freetype2-git, lib32-freetype2-minimal-git, lib32-freetype2-v35)
- lib32-gcc-libs (lib32-gcc-libs-git, lib32-gccrs-libs-git)
- lib32-gettext
- lib32-glu (lib32-glu-git)
- lib32-lcms2
- lib32-libpcap
- lib32-libsm
- lib32-libxcursor (lib32-libxcursor-git)
- lib32-libxdamage
- lib32-libxi
- Show 110 more dependencies...
Required by (307)
- 0cc-famitracker (requires wine)
- 2gis (requires wine)
- 602xmlfiller (requires wine)
- adobe-reader-11 (requires wine)
- ag-dsp-controller (requires wine)
- ags-git (requires wine) (optional)
- airwave-git (requires wine)
- algodoo-wine (requires wine)
- aliyundrive-wine (requires wine)
- altirra (requires wine)
- ankama-launcher (requires wine) (optional)
- aoe3-wine-steam (requires wine)
- ares (requires wine)
- arlequin (requires wine)
- asim (requires wine)
- avidemux-core-git (requires wine) (optional)
- bahn-regio-entfernungsrechner-bin (requires wine)
- balsamiqmockups (requires wine)
- bgb (requires wine)
Latest Comments
ramatullah commented on 2022-06-04 14:19 (UTC)
Has somebody encountered this?
dbermond commented on 2022-03-28 15:13 (UTC)
@xantares repository wine is compiled with lto disabled, so this flag is not needed. You can compare with repository wine-staging, which does not used this compiler flag, and is basically the same.
xantares commented on 2022-03-28 14:54 (UTC)
wine has -ffat-lto-objects c flag, I dont know if it should be added there too
DarkShadow44 commented on 2022-01-22 19:28 (UTC) (edited on 2022-01-22 19:58 (UTC) by DarkShadow44)
For build I have to add
-I/usr/include/freetype2
to CFLAGS. No idea what exactly broke, but this is needed for the 64Bit build.EDIT: Apparently I lost some files from
libsysprof-capture
. No idea how, but reinstalling that fixed it...Neko-san commented on 2022-01-06 22:46 (UTC) (edited on 2022-01-06 22:50 (UTC) by Neko-san)
@rtentser I modified this PKGBUILD yesterday for a different purpose (applying a patch), but you can easily modify what I used for the same purpose (I removed my stuff that's irrelevant to you).
Just edit
pkgver
,_pkgver
, and the checksum for that tarball; then, delete the hidden.SRCINFO
file from the snapshot here and run:makepkg --printsrcinfo &> .SRCINFO
, renamewine-git.install
towine.install
, then you can make the package.dbermond commented on 2021-03-30 00:01 (UTC)
@katt implemented.
katt commented on 2021-03-29 13:46 (UTC)
Could you include the recent fontconfig changes? https://github.com/archlinux/svntogit-community/commit/07fccfd3a8e0951146a6d907bae3b6858c20232a
dbermond commented on 2021-01-09 15:19 (UTC)
@rtentser This package is not for building older versions of wine, and neither for bisecting, but it's for building the latest git master code.
rtentser commented on 2021-01-09 05:49 (UTC)
@katt I want to be able to build older versions of wine from this package for bisecting.
katt commented on 2021-01-08 22:12 (UTC)
@rtentser Sounds like you want wine-stable.
rtentser commented on 2021-01-02 05:32 (UTC)
Can't build wine-5.0 with this.
winebuild: /usr/bin/ld failed with status 1 winegcc: ../../tools/winebuild/winebuild failed make[1]: [Makefile:755: crypt32.dll.so] Error 2 make[1]: Leaving directory '/home/rtentser/Sources/AUR/wine-git/src/build-64/dlls/crypt32' make: [Makefile:9177: dlls/crypt32] Error 2 ../../tools/winegcc/winegcc -o ctapi32.dll.fake --wine-objdir ../.. -m64 -fPIC -fasynchronous-unwind-tables \ -shared ../../../wine/dlls/ctapi32/ctapi32.spec ctapi32.o -ladvapi32 \ ../../libs/port/libwine_port.a -Wl,-O1,--sort-common,--as-needed,-z,relro make: *** Waiting for unfinished jobs.... ../../../tools/winegcc/winegcc -o cryptui_test-stripped.exe --wine-objdir ../../.. -b x86_64-w64-mingw32 \ --lib-suffix=.cross.a -s -Wb,-F,cryptui_test.exe -mno-cygwin cryptui.cross.o testlist.cross.o \ ../../../dlls/cryptui/libcryptui.cross.a ../../../dlls/crypt32/libcrypt32.cross.a \ ../../../dlls/user32/libuser32.cross.a ../../../tools/winegcc/winegcc -o cryptui_test.exe --wine-objdir ../../.. -b x86_64-w64-mingw32 \ --lib-suffix=.cross.a -mno-cygwin cryptui.cross.o testlist.cross.o \ ../../../dlls/cryptui/libcryptui.cross.a ../../../dlls/crypt32/libcrypt32.cross.a \ ../../../dlls/user32/libuser32.cross.a echo "cryptui_test.exe TESTRES \"cryptui_test-stripped.exe\"" | ../../../tools/wrc/wrc -o ../../../programs/winetest/cryptui_test.res make[1]: Leaving directory '/home/rtentser/Sources/AUR/wine-git/src/build-64/dlls/cryptui/tests' make[1]: Leaving directory '/home/rtentser/Sources/AUR/wine-git/src/build-64/dlls/ctapi32' ==> ERROR: A failure occurred in build(). Aborting...
dbermond commented on 2020-01-03 19:52 (UTC)
@ekce xorgproto is being automatically pulled. Package is currently building fine without modifications.
ekce commented on 2019-12-21 18:29 (UTC)
This package now requires xorgproto.
dbermond commented on 2019-04-19 17:04 (UTC) (edited on 2019-04-19 17:05 (UTC) by dbermond)
@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)
I noticed that the version on this package is 3.18 prefix but current version of wine is 4.6 https://www.winehq.org/announce/4.6
Maybe if you want to drop the subversion and keep the main number which will increment annually that might be a good idea or use something else to minimize confusion I'd like to suggest it.
Tom_B commented on 2018-10-22 13:23 (UTC)
I'm not sure why but using this package, I cannot use Steam in offline mode. The standard arch package works fine but with wine-git steam via wine doesn't connect. Is there something I can add to the ./configure or make line to enable networking?
I'm not sure if it's a problem with wine itself or this package but it makes it slightly difficult to try custom patches in wine if you need to test a steam game.
dbermond commented on 2018-10-11 21:41 (UTC)
@Morguldir Thank you for reporting this. Package updated.
morguldir commented on 2018-10-10 16:56 (UTC)
They applied the freetype patch upstream
https://source.winehq.org/git/wine.git/commitdiff/66e446c5ec5c7f4f072358712151d75305dfbd49?hp=935eed8e980a62557b19b3313e32106752b4e4f6
dbermond commented on 2018-07-03 17:12 (UTC)
@Enverex If you are building with avx support enabled then you're modifying the default Arch Linux build flags. By doing this you're pretty aware of the issues that it can cause (like the one you're having). Users wanting the most vanilla experience should 1) not modify the build flags, and/or 2) build the package in a clean chroot. It's user reponsibility to control the build flags, unless some major intervention is required.
Forcedly disabling avx support is not a good idea. Firstly, because it's not intended to use avx by default in any way (due to the default Arch build flags being x86_64 generic ones). Secondly, because it will impact users that want to benefit from avx support. Thirdly, because this is affecting only your application. If it would be a broad wine issue affecting a huge amount of applications, then well, we could disable avx here, but this is not the case.
I suggest you to fill a bug report in upstream wine saying that you're having issues in your application when avx is enabled, instead of asking for forcedly disabling avx here.
Enverex commented on 2018-06-29 12:49 (UTC)
@dbermond - Wine will literally just crash if it tries to use it, there is no benefit to leaving it enabled. You have 2 possible situations:
The user doesn't have an AVX capable CPU, the flag won't do anything because AVX was never supported in the first place.
The user has an AVX capable CPU. As soon as Wine tries to use AVX, Wine will crash. Adding the flag negates this situation.
Essentially leaving AVX enabled will do nothing other than cause Wine to crash whenever it's used (universally, until it's fixed upstream, if that will actually happen). There is zero positive to enabling the flag (which will be enabled by default for anyone using native or CPU specific compiler flags).
But it's up to you.
dbermond commented on 2018-06-05 15:26 (UTC)
@Enverex I don't think it's a good idea to force users to compile without avx support. It can be a user choice to use avx.
Enverex commented on 2018-06-04 14:32 (UTC)
@dbermond - I've actually tracked down the real reason now. It will technically affect anyone with an AVX capable processor but only triggers in very rare circumstances: https://bugs.winehq.org/show_bug.cgi?id=45289
May be worth adding "-mno-avx" to C/XXFLAGS in the build section somewhere to negate it.
dbermond commented on 2018-06-03 02:28 (UTC)
@Enverex I'm glad that you found the answer. But yes, this package is the same as wine from the official repositories, except for being the development version.
Packages from the official repositories are built in a clean chroot to avoid linking against undesired libraries and other interferences that may occur. For example, in a chroot it will not link against any nvidia specific library that the user might have installed. In order to better reproduce the official repository package, the user should build it in a clean chroot. And as you know, official repository packages are built with generic x86_64 compiler flags, and this can also cause runtime differences.
Enverex commented on 2018-06-02 22:25 (UTC) (edited on 2018-06-02 23:07 (UTC) by Enverex)
Cemu crashes in Mario Kart 8 with this (even when set to the 3.9 release commit specificall) but not the stock repo Wine.
The actual build looks pretty much the same between this and the stock Arch repo version. Is there anything else different in the build script here that could be responsible for this different behaviour?
EDIT: Looks like it may be a GCC issue. It only happens if compiled with -march=native (i7-8700K).
dbermond commented on 2017-12-11 19:26 (UTC)
@EndlessEden Segfault at compile time? Package is building fine for me.
EndlessEden commented on 2017-12-11 09:03 (UTC)
i segfault with this. idk why...
dbermond commented on 2017-10-10 20:35 (UTC)
Vash63 commented on 2017-09-28 06:09 (UTC)
Vash63 commented on 2017-09-27 09:57 (UTC)
sidneycrestani commented on 2017-02-16 00:00 (UTC)
greyltc commented on 2017-02-12 14:32 (UTC)
greyltc commented on 2017-02-12 12:35 (UTC)
z3ntu commented on 2017-01-11 13:09 (UTC)
sidneycrestani commented on 2016-12-07 00:04 (UTC)
C0rn3j commented on 2016-12-06 17:11 (UTC)
sidneycrestani commented on 2016-12-06 00:22 (UTC) (edited on 2016-12-06 01:01 (UTC) by sidneycrestani)
C0rn3j commented on 2016-12-05 22:28 (UTC)
C0rn3j commented on 2016-12-04 00:46 (UTC)
C0rn3j commented on 2016-11-20 13:36 (UTC)
sxe commented on 2016-05-14 09:38 (UTC)
Xylemon commented on 2016-04-08 18:11 (UTC) (edited on 2016-04-08 18:14 (UTC) by Xylemon)
dickiteemerald commented on 2016-03-13 03:03 (UTC)
davispuh commented on 2015-07-27 22:33 (UTC)
Soukyuu commented on 2015-06-05 11:48 (UTC)
Soukyuu commented on 2015-05-27 15:44 (UTC)
sxe commented on 2015-01-11 10:58 (UTC)
xymostech commented on 2014-05-29 01:30 (UTC)
acidicX commented on 2014-04-05 17:23 (UTC)
sxe commented on 2014-02-04 10:26 (UTC)
oscode commented on 2014-01-24 19:42 (UTC)
sxe commented on 2014-01-18 10:46 (UTC)
haagch commented on 2014-01-16 20:53 (UTC)
sxe commented on 2013-12-07 09:57 (UTC)
haagch commented on 2013-12-05 13:45 (UTC)
hepha commented on 2013-12-01 14:56 (UTC)
jonnybarnes commented on 2013-05-12 18:14 (UTC)
jonnybarnes commented on 2013-05-12 17:04 (UTC)
jonnybarnes commented on 2013-05-11 15:34 (UTC)
sxe commented on 2013-04-24 17:38 (UTC)
TheWaffleGuy commented on 2013-04-22 18:50 (UTC)
sxe commented on 2013-04-22 17:16 (UTC)
TheWaffleGuy commented on 2013-04-22 15:50 (UTC)
Wintershade commented on 2013-04-21 10:03 (UTC)
sxe commented on 2013-04-20 10:19 (UTC)
jleclanche commented on 2013-04-19 22:20 (UTC)
commented on 2013-03-15 00:16 (UTC)
sxe commented on 2013-01-02 11:11 (UTC)
quetzal commented on 2012-12-19 18:00 (UTC)
TheJJ commented on 2012-10-05 23:17 (UTC)
sxe commented on 2012-07-27 18:23 (UTC)
commented on 2012-07-27 13:58 (UTC)
sxe commented on 2012-04-17 08:25 (UTC)
Aelius commented on 2012-04-17 00:54 (UTC)
sxe commented on 2012-03-17 10:11 (UTC)
commented on 2012-03-16 01:33 (UTC)
dot commented on 2012-02-06 09:24 (UTC)
vodik commented on 2012-02-04 13:02 (UTC)
dot commented on 2012-02-01 18:51 (UTC)
commented on 2012-01-31 10:00 (UTC)
sxe commented on 2012-01-01 21:52 (UTC)
commented on 2012-01-01 14:41 (UTC)
korrode commented on 2011-12-27 12:54 (UTC)
sxe commented on 2011-11-12 10:26 (UTC)
commented on 2011-11-09 20:35 (UTC)
rwd2 commented on 2011-10-13 09:45 (UTC)
sxe commented on 2011-10-11 18:52 (UTC)
xphoniexx commented on 2011-10-11 03:30 (UTC)
sxe commented on 2011-10-06 09:39 (UTC)
feilen commented on 2011-10-06 06:52 (UTC)
sxe commented on 2011-09-06 07:03 (UTC)
commented on 2011-08-12 15:17 (UTC)
sxe commented on 2011-08-03 18:58 (UTC)
tea commented on 2011-08-03 16:57 (UTC)
sxe commented on 2011-08-03 15:10 (UTC)
tea commented on 2011-08-03 14:31 (UTC)
sxe commented on 2011-08-02 10:29 (UTC)
tea commented on 2011-08-01 22:41 (UTC)
feilen commented on 2011-07-17 19:35 (UTC)
commented on 2011-02-13 10:22 (UTC)
sxe commented on 2011-01-25 22:13 (UTC)
commented on 2011-01-25 22:03 (UTC)
commented on 2011-01-21 08:23 (UTC)
sxe commented on 2010-12-18 11:53 (UTC)
commented on 2010-12-17 17:23 (UTC)
sxe commented on 2010-12-11 18:57 (UTC)
sxe commented on 2010-12-06 20:52 (UTC)
lubosz commented on 2010-12-06 20:16 (UTC)
lubosz commented on 2010-12-06 19:53 (UTC)
sxe commented on 2010-11-23 10:33 (UTC)
commented on 2010-11-23 06:35 (UTC)
sxe commented on 2010-10-20 15:33 (UTC)
commented on 2010-10-20 14:13 (UTC)
sxe commented on 2010-09-28 15:54 (UTC)
xyproto commented on 2010-09-14 16:51 (UTC)
sxe commented on 2010-08-15 12:45 (UTC)
intellitech commented on 2010-07-26 16:12 (UTC)
commented on 2010-07-25 23:30 (UTC)
commented on 2010-07-21 11:51 (UTC)
commented on 2010-07-16 13:58 (UTC)
intellitech commented on 2010-07-13 17:12 (UTC)
IncredibleLaser commented on 2010-07-04 13:32 (UTC)
Noctivivans commented on 2010-06-21 12:55 (UTC)