On Wed, Nov 04, 2009 at 03:07:58PM +0100, Steve Wolter wrote: > Dear Robert, if you are going to include the shared libgcc > in the standard distribution, please note that in the > current mingw32 upstream the libgcc is linked against the > non-thread-safe libmingw32.a, resulting in DLL exception safety > and thread safety being mutually exclusive. See the discussion on > http://n2.nabble.com/gcc-4-4-multi-threaded-exception-handling-thread-specifier-not-working-td3440749.html > for details.
Is there a bug about this in GCC Bugzilla? On Wed, Nov 04, 2009 at 03:16:53PM +0100, Steve Wolter wrote: > # MinGW-specific parts of LIB_SPEC > -SHLIB_LC = -lmingw32 -lmingwex -lmoldname -lmsvcrt -luser32 -lkernel32 > -ladvapi32 -lshell32 > +SHLIB_LC = -lmingwthrd -lmingw32 -lmingwex -lmoldname -lmsvcrt -luser32 > -lkernel32 -ladvapi32 -lshell32 I'm not convinced about this. If we're building a multithreaded program and libmingw32.a is not thread-safe, why are we still linking with it? -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
