On 2011/09/25 23:47, Stephen Kitt <st...@sk2.org> wrote: > I've found traces of similar bugs in gcc 4.4.4, for example > https://bugzilla.mozilla.org/show_bug.cgi?id=654493 - this doesn't > seem specific to gcc-mingw32. In fact g++-4.4 in Debian (4.4.6) still > has the same bug!
That's right - the bug is in gcc4.4's libstdc++. Seems to be fixed from 4.5 on. With mingw32, I seemed to be stuck with the old gcc4.4. > gcc-mingw32 is now in simple maintenance mode, and I intend to have it > removed once all its reverse build-dependencies have switched to > gcc-mingw-w64 (which can build 32-bit executables and DLLs). Would it > be possible for you to give gcc-mingw-w64 a try? The bug does not occur here (it's gcc 4.6). The binaries have confusing names, though: "i686-w64-..." is unable to generate 64 bit binaries, despite the "w64" name part. If gcc-mingw-w64 is the designated full-featured successor of gcc-mingw32, we can close this bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
