On Tue, Nov 4, 2014 at 3:54 PM, Alexander Shukaev <[email protected]> wrote: >> No, you are entirely incorrect and spreading misinformation I'm >> afraid. For MinGW-w64 to operate correctly, the only type of PECOFF >> that should ever be linked with -static-libgcc is an entirely static >> executable. It's got nothing to do with philosophy or preference, it's >> to do with segfaults in your code or passing segfaults onto people who >> use your code (as the tcl/tk developers did to Oscar). > > > I'm well aware of that. What misinformation do I spread? I said that > standalone packages (like executables and shared libraries, which are not > supposed to be used outside of the package itself) for end users are fine to > be released with "-static*" linking. If you think that this is wrong and can > cause problems, then please post exhaustive explanation why including some > technical details and an example of a use case where things can break. > Otherwise, this sounds more like an alarmist claim. Thanks in advance.
The details area already in this thread: https://www.mail-archive.com/[email protected]/msg68284.html The fix to GCC's specs to ensure that libgcc_s is not stripped out since it is critical that this doesn't happen is: https://github.com/Alexpux/MSYS2-packages/commit/0609112c3ca66dd1750f1eaf31bc5db8db4da59c The same fix was required for MSYS2 GCC and MinGW-w64 GCC. On MinGW-w64, using -static or -static-libgcc is a great idea if and only if you are building an entirely static executable that doesn't load plugins. I'm not going to setup test cases for you, no. This bug's already cost me a weekend during which I discussed the problem in considerable detail with the MinGW-w64 developers. ------------------------------------------------------------------------------ _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
