-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dave Korn wrote: > Plain C applications will, by default, be linked statically against libgcc as > previously. To link against the shared libgcc DLL, '-shared-libgcc' must be > manually specified on the command-line.
1) What exactly are the pros and cons of this? IOW, why should we *not* want to use shared libgcc? 2) How can -shared-libgcc (or -static-libgcc, for that matter) be passed when building with libtool so that it actually gets passed on to gcc? > The to-do list for the first fully stable release currently stands at: > > - Implement improved weak symbol handling in Win32 PE binutils, to resolve C++ > operator new/delete interposition problem with shared libstdc++. > - Add support scripts for default compiler switching. std::wstring for cygwin-1.7? Please?? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkm5VbAACgkQpiWmPGlmQSO8+QCg8Etp2BF5O/JoJAL/L5UQPhyu GdwAoKvgtJ1+waD7Yl4Uf20tSQoLSiHH =ZQME -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
