This is the mail archive of the
mailing list for the Cygwin project.
Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)
- From: JonY <jon_y at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 01 Feb 2010 08:48:35 +0800
- Subject: Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)
- References: <4B5AC690.firstname.lastname@example.org> <4B5CEDF3.email@example.com> <4B5CF525.firstname.lastname@example.org> <4B5D1B18.email@example.com> <4B5F0548.firstname.lastname@example.org> <4B5F0ABE.email@example.com>
On 1/26/2010 23:31, JonY wrote:
On 1/26/2010 23:07, Dave Korn wrote:
On 25/01/2010 04:16, JonY wrote:
This could be changed in the upstream GCC with libw32stdc++-6 as 32bit
mingw-w64 toolchain, libw64stdc++-6 as 64bit mingw-w64, and the normal
libstdc++-6 for the mingw.org toolchain. Now all 3 can live side by
That seems like a logical and consistent extension of the existing
cyg*-vs-lib* DLL namespacing convention.
there is also a related bug with libgcc which does not use libtool. See
Basically, the same issue with mingw based toolchains using
libgcc_s_<EH>-1.dll, clobbering each other on multilib mingw-w64 GCC
packaging put on hold for awhile. I need to file some FSF copyright
papers before I can fix the DLL clash issue on GCC.
Sorry for the inconvenience.