http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |i686-w64-mingw32
Status|WAITING |NEW
CC| |ktietz at gcc dot gnu.org
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to DrD from comment #10)
> Target: i686-w64-mingw32
> Configured with: ../../../src/gcc-4.7.2/configure --host=i686-w64-mingw32
> --build=i686-w64-mingw32 --target=i686-w64-mingw32
> --prefix=/temp/x32-4.7.2-posix-sjlj-r8/prefix
> --with-sysroot=/temp/x32-4.7.2-posix-sj
> lj-r8/prefix --enable-shared --enable-static --enable-targets=all
> --enable-multilib --enable-languages=c,c++,fortran,lto
> --enable-libstdcxx-time=yes --enable-threads=posix
Thanks, that's what I needed, it confirms it's mingw-w64 with pthread support.
Kai, do you have any ideas for how to track down the "leak" here?
My knowledge of mingw-w64 and Windows in general is close to zero.
