can you explain why the automated builds targeting win64cygwin has i686 target
files in
it?https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Automated%20Builds/
-
Jim Michaels
jmich...@yahoo.com
j...@renewalcomputerservices.com
http://RenewalComputerSer
On 01/02/2015 03:46 AM, Jacek Caban wrote:
> In general the problem is hard to solve. About any new wine-gecko
> release needs fixes on mingw-w64 side. That's why the only thing that I
> can guarantee when I do the release is that it works with recent master
> version of mingw-w64. We're going to h
Jacek Caban schreef op vr 02-01-2015 om 10:46 [+0100]:
> On 01/01/15 18:30, Erik van Pienbroek wrote:
> > Apparently wine-gecko fails to build when these symbols are only
> > available with _WIN32_WINNT >= 0x0600. @Jacek: could this be a
> > wine-gecko bug? I've workaround'ed this issue in Fedora 2
Adrien Nader schreef op ma 15-12-2014 om 22:09 [+0100]:
> Maybe smaller and more frequent releases? It seemed to me that a release
> every 6-month or so (very roughly) would fit. I'm not arguing for strict
> time-based release but rather looking at the tree something like 6
> months after the last
AFAI remember was this header necessary for some of this header users.
Have you tried to bootstrap binutils/gcc with this change? I remember
there was a reason to depend on this header, but I can recall why
exactly.
Anyway, if boostrap of binutils/gcc is fine without regressions, then
I am ok with
On 01/01/15 18:30, Erik van Pienbroek wrote:
> Apparently wine-gecko fails to build when these symbols are only
> available with _WIN32_WINNT >= 0x0600. @Jacek: could this be a
> wine-gecko bug? I've workaround'ed this issue in Fedora 20 using
> attached 0021-Lower-_WIN32_WINNT-requirements-for-Un-
