Updating from samba-4.13.9 to 4.13.9-r1 fails because during the normal build a cross-compiler is detected and in turn used for building... See the build.log. Same for 4.14.5-r1 here. Hm... Reproducible: Always
Created attachment 719232 [details] build.log
Please attach output of `emerge --info` as well, I can't seem to reproduce despite having i686-w64-mingw32-gcc installed.
Created attachment 719400 [details] emerge --info Voila the output of emerge --info. Thanks for investigating.
A temporary workaround is: mv /usr/bin/i686-w64-mingw32-gcc /usr/bin/i686-w64-mingw32-gcc-DISABLED Then emerge samba works. When undoing the workaround, emerge samba fails again. I just don't understand why the presence of a mingw32 cross-compiler has any impact on building samba for the native linux amd64 host.
The issue disappeared. What I did is: crossdev --clean i686-w64-mingw32 and then reinstalled the cross-compiler again. Obviously with newer binutils, gcc and libc versions then originally, most importantly probably using gcc 10.3 instead of 9.3. After that emerge -a samba worked. Maybe crossdev --clean fixed some things like dangling symlinks or so. Note: I have half a dozen cross-compilers and just wiped the i686-w64-mingw32 temporarily. So, while not actually knowing what caused the issue, I'd close this bug report.
Thanks for looking into it, if there's an issue I imagine it may be with what older crossdev did (and was kept around) and it's not really samba's problem.
