On 3/17/2016 16:07, Tony Kelman wrote:
> Tony Kelman kelman.net> writes:
>
>>
>>> I have just updated the mingw-w64 headers, runtime, and winpthreads to
>>> 4.0.5-1.
>>>
>>> mingw64-*-headers-4.0.5-1
>>> mingw64-*-runtime-4.0.5-1
>>> mingw64-*-winpthreads-4.0.5-1
>>
>> Question, since I just had
Tony Kelman kelman.net> writes:
>
> > I have just updated the mingw-w64 headers, runtime, and winpthreads to
> > 4.0.5-1.
> >
> > mingw64-*-headers-4.0.5-1
> > mingw64-*-runtime-4.0.5-1
> > mingw64-*-winpthreads-4.0.5-1
>
> Question, since I just had issues building some of LLVM's unit tests
> I have just updated the mingw-w64 headers, runtime, and winpthreads to
> 4.0.5-1.
>
> mingw64-*-headers-4.0.5-1
> mingw64-*-runtime-4.0.5-1
> mingw64-*-winpthreads-4.0.5-1
Question, since I just had issues building some of LLVM's unit tests and
tracked the root cause back to here - is it
I have just updated the mingw-w64 headers, runtime, and winpthreads to
4.0.5-1.
mingw64-*-headers-4.0.5-1
mingw64-*-runtime-4.0.5-1
mingw64-*-winpthreads-4.0.5-1
The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
I have just updated the mingw-w64 headers, runtime, and winpthreads to
4.0.5-1.
mingw64-*-headers-4.0.5-1
mingw64-*-runtime-4.0.5-1
mingw64-*-winpthreads-4.0.5-1
The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
5 matches
Mail list logo