Created attachment 394056 [details] cross-x86_64-w64-mingw32-gcc-stage2.log.xz As the title says, running crossdev -t x86_64-w64-mingw32 fails to build cross-x86_64-w64-mingw32/gcc-4.8.4 (stage 2). Steps to reproduce: crossdev -t x86_64-w64-mingw32 End of output: libtool: link: /usr/libexec/gcc/x86_64-w64-mingw32/ranlib .libs/libgfortran.a libtool: link: ( cd ".libs" && rm -f "libgfortran.la" && ln -s "../libgfortran.la" "libgfortran.la" ) make[5]: Leaving directory '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/build/x86_64-w64-mingw32/libgfortran' make[4]: Leaving directory '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/build/x86_64-w64-mingw32/libgfortran' make[3]: Leaving directory '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/build' Makefile:852: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/build' * ERROR: cross-x86_64-w64-mingw32/gcc-4.8.4::x-portage failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=cross-x86_64-w64-mingw32/gcc-4.8.4::x-portage'`, * the complete build log and the output of `emerge -pqv '=cross-x86_64-w64-mingw32/gcc-4.8.4::x-portage'`. * The complete build log is located at '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/temp/environment'. * Working directory: '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/build' * S: '/var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/gcc-4.8.4' * * Please include /var/tmp/portage/cross-x86_64-w64-mingw32/gcc-4.8.4/work/gcc-build-logs.tar.bz2 in your bug report. *
Created attachment 394058 [details] cross-x86_64-w64-mingw32-info.log
Created attachment 394060 [details] gcc-config.logs.tar.xz
I was able to get MinGW crossdev gcc to build successfully by disabling libsanitizer. I added these to /etc/portage/package.use: cross-x86_64-w64-mingw32/gcc -sanitize cross-i686-w64-mingw32/gcc -sanitize Despite the error message hinting that this was an x64 problem, I had to disable libsanitizer on for both my 32-bit and 64-bit MinGW crossdev environments. Frankly I'm not familiar with libsanitizer, so I don't know if this should be made default or if this is a bug that needs to be fixed.
*** Bug 541786 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 525910 ***
*** Bug 526142 has been marked as a duplicate of this bug. ***
*** Bug 587900 has been marked as a duplicate of this bug. ***