Hi,
when trying to build a DLL (I think it'd be the same thing with an EXE though) with the -static-libgcc flag using the mingw-w64 cross-compiler in the Fedora 17 repository, I ran into symbol conflicts between libgcc_eh.a and libgcc_s.a: there are errors about multiple definitions of several "_Unwind_*" symbols. Unfortunately, the code uses exceptions, so -fno-exceptions is not an option.
http://tdm-gcc.tdragon.net/development says that TDM-GCC (maintainer CCed) has a local patch for what appears to be this same issue:
Includes a patch which reintegrates the code from libgcc_eh.a into libgcc.a and the libgcc DLL. As long as the shared memory region is used to handle exceptions, this library is unnecessary, and it causes multiple definition errors for the symbols in it because it hasn't been added to binutils' exception libraries yet.
Therefore I am asking whether we can get that fix (or some other fix for this bug): 1. into the Fedora mingw64-gcc packaging and 2. into upstream GCC?
Kevin Kofler
Hi,
Kevin Kofler wrote:
when trying to build a DLL (I think it'd be the same thing with an EXE though) with the -static-libgcc flag using the mingw-w64 cross-compiler in the Fedora 17 repository, I ran into symbol conflicts between libgcc_eh.a and libgcc_s.a: there are errors about multiple definitions of several "_Unwind_*" symbols. Unfortunately, the code uses exceptions, so -fno-exceptions is not an option.
This is still broken in the mingw64-gcc-4.7.2-2.fc17 update.
I filed https://bugzilla.redhat.com/show_bug.cgi?id=879084 for this issue.
Kevin Kofler
-
Kevin Kofler