wine-1.1.42 fails to emerge on a mostly-stable amd64 system. This happens every time with: emerge -1av --keep-going --jobs=3 --load-average=5 wine The latter three options are default opts, but the failure occurs even when I pass --ignore-default-opts. Here is a snippet from the log showing the first failure: ../../tools/winegcc/winegcc -B../../tools/winebuild --sysroot=../.. -shared ./user32.spec button.o caret.o class.o clipboard.o combo.o cursoricon.o dde_client.o dde_misc.o dde_server.o defdlg.o defwnd.o desktop.o dialog.o driver.o edit.o exticon.o focus.o hook.o icontitle.o input.o listbox.o lstr.o mdi.o menu.o message.o misc.o msgbox.o nonclient.o painting.o property.o resource.o scroll.o spy.o static.o sysparams.o text.o uitools.o user_main.o win.o winhelp.o winpos.o winproc.o winstation.o wsprintf.o resources/user32_Bg.res resources/user32_Ca.res resources/user32_Cs.res resources/user32_Da.res resources/user32_De.res resources/user32_En.res resources/user32_Eo.res resources/user32_Es.res resources/user32_Fi.res resources/user32_Fr.res resources/user32_Hu.res resources/user32_It.res resources/user32_Ja.res resources/user32_Ko.res resources/user32_Lt.res resources/user32_Nl.res resources/user32_No.res resources/user32_Pl.res resources/user32_Pt.res resources/user32_Ro.res resources/user32_Ru.res resources/user32_Si.res resources/user32_Sk.res resources/user32_Sv.res resources/user32_Tr.res resources/user32_Uk.res resources/user32_Wa.res resources/user32_Zh.res resources/user32_bin.res resources/version.res -o user32.dll.so -limm32 -lgdi32 -ladvapi32 -lkernel32 -lntdll -Wb,-dimm32 ../../libs/port/libwine_port.a -Wl,-O1 winebuild: sysparams.o is an empty file winegcc: ../../tools/winebuild/winebuild failed make[1]: *** [user32.dll.so] Error 2 Reproducible: Always Steps to Reproduce: 1. emerge -1av wine Actual Results: Build fails Expected Results: Successful build. I am able to build wine-1.1.42 from git as a user.
Created attachment 227939 [details] emerge --info
Created attachment 227941 [details] build.log showing failure
Did you try to compile the package with ccache being disabled?
(In reply to comment #3) > Did you try to compile the package with ccache being disabled? > That did it... ccache had never given me trouble like that before, even with previous versions of wine. Is ccache generally safe to leave enabled, or are problems like this common? Thanks, and sorry for the inconvenience.
(In reply to comment #4) > Is ccache generally safe to leave enabled, or are problems like this common? Such problems apprear at odd times. There's no need to completely disable ccache just remember to try compilation without ccache before you file a bug report. There are situations where you should clean the ccache like when updating gcc because otherwise you still have the code generated with the old compiler in the cache. As this is no error in wine I mark his bug as INVALID.
