wine git 26/01/17 does not complie

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
Linubie
Newbie
Newbie
Posts: 1
Joined: Sun Aug 31, 2008 3:27 am

wine git 26/01/17 does not complie

Post by Linubie »

while compiling it stops with:

Code: Select all

make[1]: Entering directory '/var/tmp/portage/app-emulation/wine-9999/work/wine-9999-abi_x86_32.x86/dlls/mf3216'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/var/tmp/portage/app-emulation/wine-9999/work/wine-9999-abi_x86_32.x86/dlls/mf3216'
STRIPPROG="strip" /var/tmp/portage/app-emulation/wine-9999/work/wine-9999/tools/install-sh  dlls/mf3216/mf3216.so /var/tmp/portage/app-emulation/wine-9999/image//usr/lib32/wine/mf3216.so
/var/tmp/portage/app-emulation/wine-9999/work/wine-9999/tools/install-sh: dlls/mf3216/mf3216.so does not exist.
make: *** [Makefile:10219: dlls/mf3216/install-lib] Error 1
User avatar
Bob Wya
Level 12
Level 12
Posts: 3068
Joined: Sat Oct 16, 2010 7:40 pm

Re: wine git 26/01/17 does not complie

Post by Bob Wya »

Linubie wrote:while compiling it stops with:

Code: Select all

make[1]: Entering directory '/var/tmp/portage/app-emulation/wine-9999/work/wine-9999-abi_x86_32.x86/dlls/mf3216'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/var/tmp/portage/app-emulation/wine-9999/work/wine-9999-abi_x86_32.x86/dlls/mf3216'
STRIPPROG="strip" /var/tmp/portage/app-emulation/wine-9999/work/wine-9999/tools/install-sh  dlls/mf3216/mf3216.so /var/tmp/portage/app-emulation/wine-9999/image//usr/lib32/wine/mf3216.so
/var/tmp/portage/app-emulation/wine-9999/work/wine-9999/tools/install-sh: dlls/mf3216/mf3216.so does not exist.
make: *** [Makefile:10219: dlls/mf3216/install-lib] Error 1
If you're using Wine Staging - then the stock Gentoo wine-9999 ebuild can be a bit unreliable with Git master builds. Hence why I forked the app-emulation/wine package in my Overlay (::bobwya surprisingly!!) and did a tonne of work to support building Wine Staging from the Git Master. Even so there can be the odd breakage IMHO. Typically it an happen when you build in the "middle of" Git commit bundles and gets resolved quite quickly.

Bob
Locked