Created attachment 764951 [details] samba build log Hello, I have an issue compiling samba for a while now (not that I need it, it's being pulled by something in Gnome I cannot disable), and the error message I get is the following: ``` [206/207] Compiling packaging/systemd/winbind.service.in [207/207] Compiling packaging/systemd/samba.service.in /usr/libexec/gcc/i686-w64-mingw32/ld: cannot find -lpthread collect2: error: ld returned 1 exit status ``` This may indicate that I have an issue with my mingw-gcc build (that I need to have built with posix thread model). Howewever, I can successfully build wine-staging with `mingw` useflag. I emerge mingw-gcc with the following script, if that's any useful: ``` #!/bin/bash echo "######################################" echo "Generating x86_64-w64-mingw32" echo "######################################" crossdev --target cross-x86_64-w64-mingw32 crossdev --lenv 'USE="libraries"' \ --genv 'EXTRA_ECONF="--enable-threads=posix"' \ --init-target --target cross-x86_64-w64-mingw32 env USE="libraries" emerge --oneshot cross-x86_64-w64-mingw32/mingw64-runtime env USE="libraries" emerge --oneshot cross-x86_64-w64-mingw32/gcc # i686 echo "######################################" echo "Generating i686-w64-mingw32" echo "######################################" crossdev --target cross-i686-w64-mingw32 crossdev --lenv 'USE="libraries"' \ --genv 'EXTRA_ECONF="--enable-threads=posix --disable-sjlj-exceptions --with-dwarf2"' \ --init-target --target cross-i686-w64-mingw32 env USE="libraries" emerge --oneshot cross-i686-w64-mingw32/mingw64-runtime env USE="libraries" emerge --oneshot cross-i686-w64-mingw32/gcc ``` Any idea what may be wrong ? Thank you for your help.
Created attachment 764952 [details] emerge pqv samba
Created attachment 764953 [details] emerge info samba
Bug https://bugs.gentoo.org/833284 is probably the reason behind. This bug can either be closed or maybe a more fine tuned dependency on mingw64-runtime should be set ? I suppose it's not really possible.
After fixing https://bugs.gentoo.org/833284 the problem doesn't occur any longer
