Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

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

Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

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 side. That

Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

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 > side. That seems like a logical and consiste

Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

On 25/01/2010 01:34, Yaakov (Cygwin/X) wrote: > On 24/01/2010 19:03, JonY wrote: >> and libiberty.a. > > Wouldn't this belong in /usr/$triplet/lib/? Libiberty needn't be installed or shipped at all really. It's pretty damn useless without any header file. Dunno why "make install" even bother

Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

On 1/25/2010 09:34, Yaakov (Cygwin/X) wrote: On 24/01/2010 19:03, JonY wrote: While packaging new binutils for cross mingw and mingw-w64, I've noticed there were some duplicate files, but I'm not sure how to handle them with cygport, advice welcome. It's hard to give advice without seeing what

Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

Yaakov (Cygwin/X) wrote: > On 24/01/2010 19:03, JonY wrote: >> There are also some issues for DLL'ized GCC target libs, such as >> libstdc++-6.dll. I've decided they should be disabled for mingw and >> mingw-w64 based 4.x toolchains for the moment, as they all wanted to be >> installed as libstdc++

Re: Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

On 24/01/2010 19:03, JonY wrote: While packaging new binutils for cross mingw and mingw-w64, I've noticed there were some duplicate files, but I'm not sure how to handle them with cygport, advice welcome. It's hard to give advice without seeing what you have already. How about showing us your

Some troubles with packaging toolchains (was Re: Need input on packaging mingw-w64 for Cygwin)

Hi, While packaging new binutils for cross mingw and mingw-w64, I've noticed there were some duplicate files, but I'm not sure how to handle them with cygport, advice welcome. The duplicate files are mostly under usr/share/locale/ and libiberty.a. We could fix this by making all cross toolchain

Re: Need input on packaging mingw-w64 for Cygwin

On 1/24/2010 15:03, Christopher Faylor wrote: On Sat, Jan 23, 2010 at 03:51:12PM -0500, Charles Wilson wrote: Dave Korn wrote: On 23/01/2010 19:02, Christopher Faylor wrote: On 1/23/2010 21:51, Chris Sutcliffe wrote: mingw-w64 is a fork of mingw to support

Re: Need input on packaging mingw-w64 for Cygwin

On Sun, Jan 24, 2010 at 2:03 AM, Christopher Faylor wrote: > So, follow-on question:  Can we have one toolchain which targets both > 32-bit and 64-bit?  It is certainly possible to do that on linux with > a -m32 and -m64 option.  Is it possible to do this with mingw? It's possible to do that with

Re: Need input on packaging mingw-w64 for Cygwin

On Sat, Jan 23, 2010 at 03:51:12PM -0500, Charles Wilson wrote: >Dave Korn wrote: >> On 23/01/2010 19:02, Christopher Faylor wrote: On 1/23/2010 21:51, Chris Sutcliffe wrote: >> mingw-w64 is a fork of mingw to >> support both win32 and win64. It'll o

Re: Need input on packaging mingw-w64 for Cygwin

On 1/24/2010 04:51, Charles Wilson wrote: Dave Korn wrote: On 23/01/2010 19:02, Christopher Faylor wrote: On 1/23/2010 21:51, Chris Sutcliffe wrote: mingw-w64 is a fork of mingw to support both win32 and win64. It'll obviously be setup as a cross compiler o

Re: Need input on packaging mingw-w64 for Cygwin

> From a policy standpoint...the mingw community is split, and while there > has been talk recently concerning reunification, that's all it has been: > talk.  The issues appear to be both personal and technical, from my > interested but only marginally involved viewpoint: > > Do we want to choose s

Re: Need input on packaging mingw-w64 for Cygwin

Dave Korn wrote: > On 23/01/2010 19:02, Christopher Faylor wrote: >>> On 1/23/2010 21:51, Chris Sutcliffe wrote: > mingw-w64 is a fork of mingw to > support both win32 and win64. It'll obviously be setup as a cross > compiler on Cygwin. > >> Does thi

Re: Need input on packaging mingw-w64 for Cygwin

On 23/01/2010 19:02, Christopher Faylor wrote: >> On 1/23/2010 21:51, Chris Sutcliffe wrote: mingw-w64 is a fork of mingw to support both win32 and win64. It'll obviously be setup as a cross compiler on Cygwin. > Does this mean that these are all

Re: Need input on packaging mingw-w64 for Cygwin

On Sat, Jan 23, 2010 at 09:47:17PM +0800, JonY wrote: >On 1/23/2010 21:51, Chris Sutcliffe wrote: >>> mingw-w64 is a fork of mingw to >>> support both win32 and win64. It'll obviously be setup as a cross >>> compiler on Cygwin. >>> >>> I would like to get some in

Re: Need input on packaging mingw-w64 for Cygwin

On 1/23/2010 21:51, Chris Sutcliffe wrote: mingw-w64 is a fork of mingw to support both win32 and win64. It'll obviously be setup as a cross compiler on Cygwin. I would like to get some inputs from Cygwin maintainers before I start packaging; mainly because mi

Re: Need input on packaging mingw-w64 for Cygwin

> mingw-w64 is a fork of mingw to > support both win32 and win64. It'll obviously be setup as a cross > compiler on Cygwin. > > I would like to get some inputs from Cygwin maintainers before I > start packaging; mainly because mingw-w64 is a fairly large > toolch