Re: [Mingw-w64-public] Is v1.0 recommended for 'production' usage?

2010-08-05 Thread Dmitrijs Ledkovs
On 5 August 2010 16:53, Luis Lavena wrote: > On Wed, Aug 4, 2010 at 7:39 PM, Dmitrijs Ledkovs > wrote: >> >> There are three roots of packages: >> >> 1) Sezero's custom toolchain >> 2) Automatic snapshot toolchain >> 3) Rolling release 1.0 branch and trunk of w64 >> >> 1) recent binutils, head mi

Re: [Mingw-w64-public] Is v1.0 recommended for 'production' usage?

2010-08-05 Thread Luis Lavena
On Wed, Aug 4, 2010 at 7:39 PM, Dmitrijs Ledkovs wrote: > > There are three roots of packages: > > 1) Sezero's custom toolchain > 2) Automatic snapshot toolchain > 3) Rolling release 1.0 branch and trunk of w64 > > 1) recent binutils, head mingw-w64, gcc-4.4 + loads of patches = very > stable, upd

[Mingw-w64-public] Fwd: Change from 4.4.4 to 4.6.0

2010-08-05 Thread Ehsan Azarnasab
-- Forwarded message -- From: Ehsan Azarnasab Date: Thu, Aug 5, 2010 at 9:32 AM Subject: Re: [Mingw-w64-public] Change from 4.4.4 to 4.6.0 To: Sisyphus On Tue, Jul 27, 2010 at 5:45 PM, Sisyphus wrote: > > - Original Message - > From: "Ozkan Sezer" > >>> you're supposed

Re: [Mingw-w64-public] Issues compiling Info-zip's zip 3.1c

2010-08-05 Thread Ozkan Sezer
On Thu, Aug 5, 2010 at 5:21 AM, Chris Sutcliffe wrote: >  On 8/04/10 9:10 PM, Ozkan Sezer wrote: >> What happens if you comment out lines 459 and 462 in >> win32/osdep.h and allow stdlib.h and mbstring.h to be >> included and get a proper definition of MB_CUR_MAX ? >> I don't know why it doesn't w