> I wonder if we should just bundle runtime libraries with the stage0 snapshot
> in the future?
I think we should bundle them: https://github.com/mozilla/rust/issues/9252
On Thu, Sep 19, 2013 at 7:16 AM, Vadim wrote:
> Okay, looks like my mingw 4 fix went in last night.
>
> Here's my personal r
The error is due to abi change of win32 gcc. reported here:
https://github.com/mozilla/rust/issues/9205
On Sat, Sep 14, 2013 at 4:52 PM, klutzy wrote:
> I've finished `make` on gcc 4.8.1, but `make check-fast` failed:
>
> task failed at 'assertion failed: `(left ==
s related to recent gcc.
On Sat, Sep 14, 2013 at 3:35 PM, klutzy wrote:
> some more explanation:
>
> #include causes /lib/gcc/mingw32//include/c++/fenv.h to
> be included.
> The header contains:
>
> #include
> #if _GLIBCXX_HAVE_FENV_H
> # include_next
>
know), they removed `#define
_GLIBCXX_HAVE_FENV_H 1` somewhere between 4.6.2 and 4.8.1.
so `#include_next ` does not occur, which is
`/include/fenv.h`. It contains some definitions e.g. `FE_ALL_EXCEPT`.
On Sat, Sep 14, 2013 at 3:25 PM, klutzy wrote:
> I've solved it some minutes ago :)
>
> Yes, but we can't check this into Rust repo. Maybe it can be worked around
> by -DWSAPOLLFD somewhere in makefiles...
>
> And just as a heads-up, these seems to be another problem,- with LLVM:
> http://sourceforge.net/p/mingw/bugs/2043/
>
> Vadim
>
> On Sep 13, 20
This? https://github.com/mozilla/rust/issues/9055
Windows APIs use stdcall, which implies all apis are decorated as
"_SetLastError@16", while cdecl APIs are decorated as "_SetLastError".
Our rustc is wrong so it generates llvm IR with wrong calling convention.
And when gcc prints linke error, it r
Mingw added new winapi at mswsock.h:
#if (_WIN32_WINNT >= _WIN32_WINNT_VISTA)
int WSAAPI WSAPoll(WSAPOLLFD, ULONG, INT);
#endif
but they forgot to add definition of WSAPOLLFD.
Someone submitted patch at http://sourceforge.net/p/mingw/bugs/1980/
but seems like it's not on mainstream.
Anyway, we
