Well... Sorry for all these bugs... But I need a workable environment after gcc-4.2 migration.
Created attachment 125785 [details] cross-mingw32-info.log
Created attachment 125787 [details] cross-mingw32-w32api.log
nothing is stopping you from forcing older versions of gcc via crossdev if gcc-4.2.0 is causing problems
True. But then someone else will open a bug... Or we end up with stabilized gcc that cannot cross dev (as in the previous ia64 issue). I thought the putthing on ~arch is for finding issue of this kind.
Same issue as bug#134318, right? checking for mingw32-gcc... no checking for gcc... gcc checking for mingw32-ar... mingw32-ar checking for mingw32-as... mingw32-as checking for mingw32-ranlib... mingw32-ranlib checking for mingw32-ld... mingw32-ld checking for mingw32-dlltool... mingw32-dlltool checking for mingw32-windres... mingw32-windres checking for build environment... standard # ls /usr/bin/mingw32-* /usr/bin/mingw32-addr2line /usr/bin/mingw32-gprof /usr/bin/mingw32-objdump /usr/bin/mingw32-ar /usr/bin/mingw32-ld /usr/bin/mingw32-ranlib /usr/bin/mingw32-as /usr/bin/mingw32-mingw32-cpp /usr/bin/mingw32-readelf /usr/bin/mingw32-cc /usr/bin/mingw32-mingw32-gcc /usr/bin/mingw32-size /usr/bin/mingw32-c++filt /usr/bin/mingw32-mingw32-gccbug /usr/bin/mingw32-strings /usr/bin/mingw32-cpp /usr/bin/mingw32-mingw32-gcov /usr/bin/mingw32-strip /usr/bin/mingw32-dlltool /usr/bin/mingw32-nm /usr/bin/mingw32-windres /usr/bin/mingw32-dllwrap /usr/bin/mingw32-objcopy
probably ... eselect-compiler is not supported, stop using it