2012/9/24 Jon <[email protected]>
> > > 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 call.
>
THat's what a "release" version usually implies. This is a choice I make to
keep things clear. I'm also thinking about using gdb/binutils release
versions, even if it would only lead to more consistency.
> But I also don't like wasting brain cells remembering lists-o-easy-fixes
> per toolchain, or your toolchain currently being the odd man out with code
> like that in a library such as libuv.
> mingw-builds 4.7.2: PASS
> tdm 4.7.1: PASS
> mingw 4.6.2: PASS
> rubenvb 4.7.2: FAIL
>
>
All these use either the SVN v2.x or trunk MinGW-w64. I chose not to.
Neither will any Linux distro providing MinGW-w64. Although those might
backport patches if they really want to. I am not forcing you to abandon
your previously working/fixed toolchain. You can even just copy over all of
mingw64/x86_64-w64-mingw32 or mingw32/i686-w64-mingw32 because that part
has not changed since the previous build.
> I've happily used your builds for awhile now as my reference MinGW-w64
> toolchain. Perhaps in the future when you guys see similar issues that
> impact well known libraries, a patch MinGW-w64 release can be quickly
> tagged as a way of helping downstream integrators release updates in a non
> ad-hoc manner.
>
I understand, and this happens regularly, just not always. Stable tags
can't be updated each time a specific fix has landed. For every project in
the world it takes more than one fix to release a new version. I will build
an update package or provide a new build as soon as possible after this
happens.
Please use a toolchain that works for you. And update minor versions only
when you need to.
Ruben
> Jon
>
>
> >
> > >
> > >
> > > > On 9/11/12, Jon <[email protected]> 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 -Iinclude/uv-private -g --std=gnu89
> > > -D_WIN32_WINNT=0x0600 -c
> > > > > src/win/async.c -o src/win/async.o
> > > > > ...
> > > > > gcc -Iinclude -Iinclude/uv-private -g --std=gnu89
> > > -D_WIN32_WINNT=0x0600 -c
> > > > > src/win/udp.c -o src/win/udp.o
> > > > > gcc -Iinclude -Iinclude/uv-private -g --std=gnu89
> > > -D_WIN32_WINNT=0x0600 -c
> > > > > src/win/util.c
> > > > > -o src/win/util.o
> > > > > In file included from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/mprapi.h:10:0,
> > > > > from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/iprtrmib.h:9,
> > > > > from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/iphlpapi.h:13,
> > > > > from src/win/util.c:34:
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/ras.h:988:3:
> > > > > error: unknown type name 'IsolationState'
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/ras.h:989:3:
> > > > > error: unknown type name 'ProbationTime'
> > > > > In file included from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/iphlpapi.h:16:0,
> > > > > from src/win/util.c:34:
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/netioapi.h:182:3:
> > > > > error: unknown type name 'NDIS_MEDIUM'
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/netioapi.h:183:3:
> > > > > error: unknown type name 'NDIS_PHYSICAL_MEDIUM'
> > > > > make: *** [src/win/util.o] Error 1
> > > > >
> > > > >
> > > > >
> > > > > Using this simple snippet
> > > > >
> > > > > #define _WIN32_WINNT 0x0601
> > > > >
> > > > > #include <winsock2.h>
> > > > > #include <ws2tcpip.h>
> > > > > #include <iphlpapi.h>
> > > > >
> > > > > int main(int argc, char *argv[])
> > > > > {
> > > > > return 0;
> > > > > }
> > > > >
> > > > > I'm able to replicate the failure
> > > > >
> > > > > C:\Users\Jon\Documents\CDev\sandbox>gcc --version
> > > > > gcc (rubenvb-4.7.1-2-release) 4.7.1
> > > > > ...
> > > > > C:\Users\Jon\Documents\CDev\sandbox>gcc -Wall -o iphlpapi.exe
> > > > > iphlpapi_test.c -lws2_32
> > > > > In file included from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/mprapi.h:10:0,
> > > > > from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/iprtrmib.h:9,
> > > > > from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/iphlpapi.h:13,
> > > > > from iphlpapi_test.c:5:
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/ras.h:988:3:
> > > > > error: unknown type name 'IsolationState'
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/ras.h:989:3:
> > > > > error: unknown type name 'ProbationTime'
> > > > > In file included from
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/iphlpapi.h:16:0,
> > > > > from iphlpapi_test.c:5:
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/netioapi.h:182:3:
> > > > > error: unknown type name 'NDIS_MEDIUM'
> > > > >
> > >
> c:\devkit-4.7.1\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.1/../../../../i686-w64-mingw32/include/netioapi.h:183:3:
> > > > > error: unknown type name 'NDIS_PHYSICAL_MEDIUM'
> > > > >
> > > > >
> > > > > What have I forgotten to do?
> > > > >
> > > > > Jon
> > > > >
> > > >
> > > > Should be fixed by adding missing includes to headers.
> > > > Just pushed rev. 5386 for this:
> > > >
> > >
> http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64?view=revision&revision=5385
> > > >
> > > > --
> > > > O.S.
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://ad.doubleclick.net/clk;258768047;13503038;j?
> http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
