2012/9/24 Jon
> On Mon, Sep 24, 2012 at 8:15 AM, Ruben Van Boxem
> wrote:
> > 2012/9/24 Ozkan Sezer
> >>
> >> On Mon, Sep 24, 2012 at 10:30 AM, Ruben Van Boxem
> >> wrote:
> >> > 2012/9/24 Jon
> >> >>
> >> >> > > fyi...the following libuv build fail still exists in
> >> >> > > `i686-w64-mingw
On Mon, Sep 24, 2012 at 8:15 AM, Ruben Van Boxem
wrote:
> 2012/9/24 Ozkan Sezer
>>
>> On Mon, Sep 24, 2012 at 10:30 AM, Ruben Van Boxem
>> wrote:
>> > 2012/9/24 Jon
>> >>
>> >> > > fyi...the following libuv build fail still exists in
>> >> > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7
> 2012/9/24 Ozkan Sezer
>
> > On Mon, Sep 24, 2012 at 10:30 AM, Ruben Van Boxem
> > wrote:
> > > 2012/9/24 Jon
> > >>
> > >> > > fyi...the following libuv build fail still exists in
> > >> > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
> > >> > >
> > >> >
> > >> > Yes, that's to be e
On Mon, Sep 24, 2012 at 9:15 AM, Ruben Van Boxem wrote:
> 2012/9/24 Ozkan Sezer
>>
>> FWIW, I just tagged and released v1.0.7 and v2.0.7 mingw-w64 headers and
>> crt.
>
>
> I had a feeling this would happen :P
>
> I am uploading updated mingw-w64 v2.0.7 update packages "update" on
> Sourceforge:
>
2012/9/24 Ozkan Sezer
> On Mon, Sep 24, 2012 at 10:30 AM, Ruben Van Boxem
> wrote:
> > 2012/9/24 Jon
> >>
> >> > > fyi...the following libuv build fail still exists in
> >> > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
> >> > >
> >> >
> >> > Yes, that's to be expected. There was no
On Mon, Sep 24, 2012 at 10:30 AM, Ruben Van Boxem
wrote:
> 2012/9/24 Jon
>>
>> > > fyi...the following libuv build fail still exists in
>> > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
>> > >
>> >
>> > Yes, that's to be expected. There was no new tagged MinGW-w64 release.
>> > The
>>
2012/9/24 Jon
> > > fyi...the following libuv build fail still exists in
> > > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
> > >
> >
> > Yes, that's to be expected. There was no new tagged MinGW-w64 release.
> The
> > previous easy fix still applies.
> >
> > Ruben
>
> Yes, using tagged
> > fyi...the following libuv build fail still exists in
> > `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
> >
>
> Yes, that's to be expected. There was no new tagged MinGW-w64 release. The
> previous easy fix still applies.
>
> Ruben
Yes, using tagged vs. non-tagged is an interesting ca
2012/9/23 Jon
> fyi...the following libuv build fail still exists in
> `i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
>
Yes, that's to be expected. There was no new tagged MinGW-w64 release. The
previous easy fix still applies.
Ruben
>
>
> > On 9/11/12, Jon wrote:
> > > In an custom m
fyi...the following libuv build fail still exists in
`i686-w64-mingw32-gcc-4.7.2-release-win32_rubenvb.7z`
> On 9/11/12, Jon wrote:
> > In an custom msys wrapped
> > `i686-w64-mingw32-gcc-4.7.1-2-release-win32_rubenvb.7z` toolchain I get the
> > following build fail with libuv that doesn't occu
On 9/11/12, Jon wrote:
> In an custom msys wrapped
> `i686-w64-mingw32-gcc-4.7.1-2-release-win32_rubenvb.7z` toolchain I get the
> following build fail with libuv that doesn't occur when I use a mingw.org
> based 4.6.2 toolchain.
>
> C:\Users\Jon\Documents\CDev\libuv-git>make
> gcc -Iinclude -Iinc
In an custom msys wrapped
`i686-w64-mingw32-gcc-4.7.1-2-release-win32_rubenvb.7z` toolchain I get the
following build fail with libuv that doesn't occur when I use a mingw.org based
4.6.2 toolchain.
C:\Users\Jon\Documents\CDev\libuv-git>make
gcc -Iinclude -Iinclude/uv-private -g --std=gnu89 -D_
12 matches
Mail list logo
