On Sun, Jun 6, 2010 at 3:11 PM, Bill Allombert
wrote:
> Well, mingw32 has not been updated since 2007 and is barely usable now.
> The license issues looks more like a pretext to stall it than anything else
> since it is still possible to use gcc 4.3 anyway.
I fully agree. You're welcome to provid
On Sun, Jun 06, 2010 at 11:53:08AM +, Ove Kaaven wrote:
> The lack of a suitable (i.e. non-buggy) mingw32 cross-compiler has blocked
> Wine updates for half a year now. Both the mingw32 package (gcc 4.2.1) and
> the gcc-mingw32 package (gcc 4.4.2) have a bug which was fixed in upstream
> gcc 4.
Den 29. mai 2010 17:51, skrev Julien Cristau:
On Sat, May 29, 2010 at 16:09:25 +0200, Ove Kaaven wrote:
Den 23. mai 2010 15:47, skrev Ove Kaaven:
Is it okay if I go ahead and do such a NMU?
Well, since there have been no objections for a week, I guess I'll go ahead.
I had been ready for som
On Sat, May 29, 2010 at 16:09:25 +0200, Ove Kaaven wrote:
> Den 23. mai 2010 15:47, skrev Ove Kaaven:
> >Is it okay if I go ahead and do such a NMU?
>
> Well, since there have been no objections for a week, I guess I'll go ahead.
>
> I had been ready for some feedback from the mingw32 maintainer
Den 23. mai 2010 15:47, skrev Ove Kaaven:
Is it okay if I go ahead and do such a NMU?
Well, since there have been no objections for a week, I guess I'll go ahead.
I had been ready for some feedback from the mingw32 maintainers like
"we're working on an updated mingw32, just wait a bit", or "g
[Ove Kaaven]
> Anyway, for me, the easiest way to be able to build an updated Wine
> package would be to NMU gcc-mingw32. Doing so seems to be just a
> matter of putting in a new gcc tarball in the source package, and
> I've confirmed that updating it to gcc 4.4.4 seems to work for what
> Wine nee
6 matches
Mail list logo
