It seems that in May, patch samba-4.13-winexe_option.patch was added allowing to disable winexe, and the ebuild passes --without-winexe to configure. This added an "enabled=bld.env.build_winexe" option to bld.SAMBA3_BINARY(), apparently in an attempt to not build that binary when --without-winexe is configured. However, on my system having both bld.env.WINEXE_CC_WIN32 and bld.env.WINEXE_CC_WIN64 (i.e., both i686-w64-mingw32-10.1.0 and x86_64-w64-mingw32-10.1.0 available in gcc-config -l), the build fails trying to build winexesvc32_exe. In the attached patch (to be applied on top of samba-4.13-winexe_option.patch), I only add build rules at all if bld.env.build_winexe is set. This allows samba to compile. Reproducible: Always
Created attachment 644842 [details, diff] Patch to fix compilation with --without-winexe
This also happens with the newly added net-fs/samba-4.11.11 that also uses the samba-4.13-winexe_option.patch. About to try with the suggested patch.
4.11.11 also succesfully compiled with the patch from comment 1.
Thanks for testing. I also confirmed that it is still needed for current net-fs/samba-4.12.4.
The patch is still needed for current 4.13.0, although samba-4.13-winexe_option.patch is no longer applied, meaning that the faulty patch was accepted upstream. Could somebody look into this please?
I have filed https://bugzilla.samba.org/show_bug.cgi?id=14511 now for upstream.
if it helps to anybody I was able to solve temporary via: su cd /usr/bin/ mmv '*mingw32-*' '#1wingw32-#2' emerge -av1 samba mmv '*wingw32-*' '#1mingw32-#2' just 'hide' mingw from samba temporary renaming it to wingw32, update it, and then put back.
The patch was not needed any more since somewhere in the >=samba-4.14.1 series.
