Re: [Mingw-w64-public] Building the cross win32 win64 compiler
Hello, I have found where the problem came from in my particular case: the environment variable C_INCLUDE_PATH pointed to the old path (to be used when compiling another project) instead of the new one. runing make C_INCLUDE_PATH= solved the problem in my case. Alexandre. 2011/10/14 xunxun xunxun1...@gmail.com It's my mistake. I thought this was built by you, but I don't think the edition's maintainer is TDM. On Fri, Oct 14, 2011 at 8:40 PM, JonY jo...@users.sourceforge.net wrote: On 10/14/2011 20:01, xunxun wrote: 于 2011/10/14 19:37, Alexandre Gouraud 写道: see below. I am not sure I do (or want) canadian-cross compilation. I just need a win64 native compiler, and in the manual it is said I would need to start creating a cross compiler first. No, you don't need cross compiler, because you have had a x86_64-w64-mingw32 native compiler. $ gcc -v Using built-in specs. COLLECT_GCC=C:\s2e\s2e-toolchain\mingw64\bin\gcc.exe COLLECT_LTO_WRAPPER=c:/s2e/s2e-toolchain/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: /home/drangon/work/mingw-w64-dgn/source/gcc/configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --disable-nls --enable-languages=c,c++,objc,obj-c++ --with-gmp=/home/drangon/work/mingw-w64-dgn/build/for_target --enable-twoprocess --disable-libstdcxx-pch --disable-win32-registry --prefix=/home/drangon/work/mingw-w64-dgn/target --with-sysroot=/home/drangon/work/mingw-w64-dgn/target Thread model: win32 gcc version 4.6.1 20110417 (prerelease) (GCC) If you native build the gcc, you can use --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 ps: drangon mingw64 gcc is built by jon_y. I thought they were built by tdm, which jon_y do you refer to? -- Best Regards, xunxun -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Alexandre -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Ciosco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
Hi, 2011/10/14 Alexandre Gouraud alexandre.gour...@gmail.com: Hello, I am trying to build the cross win32 win64 compiler, and have two questions: 1°/ In the howto howto: Creating a cross Win32 and Win64 compiler it is written that at some point, the PATH must be extended so that the new tools are used: export PATH=$PATH:/myprefix/bin But shouldn't this extension be the other way around: export PATH=/myprefix/bin:$PATH so that if I use an old version of the cross compiler to build a new version of it, the new version is found first in the PATH. Well, in case for cross-compilers this doesn't matter, as cross-compilers are prefixed with their target-triplet. Means to call cross-compiler from 32-bit - 64-bit means, that toolchain is prefix by x86_64-w64-mingw32-tools-name If you are building native toolchain and then want to utilize new one, it matters. So you should add new toolchain path in front of old PATH settings. 2°/ I am stuck in the compilation process of mingw-w66-crt (see below the log). My first guess is that #include search dir is not set up correctly in x86_64-w64-mingw32.exe. If I run the failing command with -M option, I can see in the dependency files that all the headers are comming from c:\s2e\s2e-toolchain\mingw64\mingw\include instead of c:\s2e\s2e-toolchain\home\aceg..\target\mingw\include excepted for the propkey.h and propkeydef.h files. Then if this is the right diagnosis, my question is how do I set up the configure script of gcc so that the search dirs do not include any other directory than those provided with --prefix and --with-sysroot ? You need to specify on configure for crt the option --host=x86_64-w64-mingw32. This indicates to autotools, that you want to build for this host. Otherwise it assumes you want to build native, which would then mean you are building for 32-bit in your case. Of course you need to specify same prefix and sysroot. You just missed to specify --host argument on configure. Thanks in advance, Regards, Kai -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
Hello, Thank you very much for your prompt response. This is much appreciated. 2011/10/14 Kai Tietz ktiet...@googlemail.com Well, in case for cross-compilers this doesn't matter, as cross-compilers are prefixed with their target-triplet. Means to call cross-compiler from 32-bit - 64-bit means, that toolchain is prefix by x86_64-w64-mingw32-tools-name I am building a cross compiler, and I have this issue. Maybe because I am building a cross compiler ... using the same cross compiler (which might be stupid but this is what I do for the time being). I switched the path order, and it solved my problem. In my /mingw64/bin I have both gcc.exe and x86_64-w64-mingw32-gcc.exe which conflicts with the one I have in my --prefix directory... You need to specify on configure for crt the option --host=x86_64-w64-mingw32. This indicates to autotools, that you want to build for this host. Otherwise it assumes you want to build native, which would then mean you are building for 32-bit in your case. Of course you need to specify same prefix and sysroot. You just missed to specify --host argument on configure. I did specify --host in the confirgure script of crt: $ cat ./build/mingw64/crt/config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by mingw-w64-runtime configure 1.0b, which was generated by GNU Autoconf 2.67. Invocation command line was $ ../../../src/mingw-w64-trunk-20110723/mingw-w64-crt/configure --host=x86_64-w64-mingw32 --prefix=/usr/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target --with-sysroot=/usr/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target -- Alexandre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
于 2011/10/14 16:59, Alexandre Gouraud 写道: Hello, Thank you very much for your prompt response. This is much appreciated. 2011/10/14 Kai Tietz ktiet...@googlemail.com mailto:ktiet...@googlemail.com Well, in case for cross-compilers this doesn't matter, as cross-compilers are prefixed with their target-triplet. Means to call cross-compiler from 32-bit - 64-bit means, that toolchain is prefix by x86_64-w64-mingw32-tools-name I am building a cross compiler, and I have this issue. Maybe because I am building a cross compiler ... using the same cross compiler (which might be stupid but this is what I do for the time being). I switched the path order, and it solved my problem. In my /mingw64/bin I have both gcc.exe and x86_64-w64-mingw32-gcc.exe which conflicts with the one I have in my --prefix directory... You need to specify on configure for crt the option --host=x86_64-w64-mingw32. This indicates to autotools, that you want to build for this host. Otherwise it assumes you want to build native, which would then mean you are building for 32-bit in your case. Of course you need to specify same prefix and sysroot. You just missed to specify --host argument on configure. I did specify --host in the confirgure script of crt: $ cat ./build/mingw64/crt/config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by mingw-w64-runtime configure 1.0b, which was generated by GNU Autoconf 2.67. Invocation command line was $ ../../../src/mingw-w64-trunk-20110723/mingw-w64-crt/configure --host=x86_64-w64-mingw32 --prefix=/usr/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target --with-sysroot=/usr/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target -- Alexandre Before cross building gcc, you should rebuild mingw64 headers and install to your prefix. -- Best Regards, xunxun -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
Hi xunxun, 2011/10/14 xunxun xunxun1...@gmail.com Before cross building gcc, you should rebuild mingw64 headers and install to your prefix. -- Best Regards, xunxun I have followed all the steps mentioned in the guide, including this one of course. So the problem does not come from not having installed mingw64 headers, but rather from the fact that the new headers are not picked up. In the search dir of my cross compiler, you would have noticed that I have: . ../../../../src/mingw-w64-trunk-20110723/mingw-w64-crt C:\s2e\s2e-toolchain\mingw64\x86_64-w64-mingw32\include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include-fixed C:/s2e/s2e-toolchain/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target/x86_64-w64-mingw32/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\mingw/include Why do I have the second one, which is the one messing up everything I think. -- Alexandre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
于 2011/10/14 17:27, Alexandre Gouraud 写道: Hi xunxun, 2011/10/14 xunxun xunxun1...@gmail.com mailto:xunxun1...@gmail.com Before cross building gcc, you should rebuild mingw64 headers and install to your prefix. -- Best Regards, xunxun I have followed all the steps mentioned in the guide, including this one of course. So the problem does not come from not having installed mingw64 headers, but rather from the fact that the new headers are not picked up. In the search dir of my cross compiler, you would have noticed that I have: . ../../../../src/mingw-w64-trunk-20110723/mingw-w64-crt C:\s2e\s2e-toolchain\mingw64\x86_64-w64-mingw32\include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include-fixed C:/s2e/s2e-toolchain/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target/x86_64-w64-mingw32/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\mingw/include Why do I have the second one, which is the one messing up everything I think. -- Alexandre You want to build linux-windows cross compiler or windows native compiler? -- Best Regards, xunxun -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
windows native 2011/10/14 xunxun xunxun1...@gmail.com 于 2011/10/14 17:27, Alexandre Gouraud 写道: Hi xunxun, 2011/10/14 xunxun xunxun1...@gmail.com Before cross building gcc, you should rebuild mingw64 headers and install to your prefix. -- Best Regards, xunxun I have followed all the steps mentioned in the guide, including this one of course. So the problem does not come from not having installed mingw64 headers, but rather from the fact that the new headers are not picked up. In the search dir of my cross compiler, you would have noticed that I have: . ../../../../src/mingw-w64-trunk-20110723/mingw-w64-crt C:\s2e\s2e-toolchain\mingw64\x86_64-w64-mingw32\include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include-fixed C:/s2e/s2e-toolchain/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target/x86_64-w64-mingw32/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\mingw/include Why do I have the second one, which is the one messing up everything I think. -- Alexandre You want to build linux-windows cross compiler or windows native compiler? -- Best Regards, xunxun -- Alexandre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
2011/10/14 Alexandre Gouraud alexandre.gour...@gmail.com: windows native 2011/10/14 xunxun xunxun1...@gmail.com 于 2011/10/14 17:27, Alexandre Gouraud 写道: Hi xunxun, 2011/10/14 xunxun xunxun1...@gmail.com Before cross building gcc, you should rebuild mingw64 headers and install to your prefix. -- Best Regards, xunxun I have followed all the steps mentioned in the guide, including this one of course. So the problem does not come from not having installed mingw64 headers, but rather from the fact that the new headers are not picked up. In the search dir of my cross compiler, you would have noticed that I have: . ../../../../src/mingw-w64-trunk-20110723/mingw-w64-crt C:\s2e\s2e-toolchain\mingw64\x86_64-w64-mingw32\include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include-fixed C:/s2e/s2e-toolchain/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target/x86_64-w64-mingw32/include c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\mingw/include Why do I have the second one, which is the one messing up everything I think. -- Alexandre You want to build linux-windows cross compiler or windows native compiler? -- Best Regards, xunxun -- Alexandre So you are trying to do Candian-cross compiler. This means you need Wine environment to call on linux native created binäry Windows-compiler. The other important thing for Candian-cross is that crt has then to be configured with --target=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 Regards, Kai -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
Hi, Kai 于 2011/10/14 18:31, Kai Tietz 写道: Candian-cross compiler By the way, what is Candian-cross compiler ? This is the first time I heared it. -- Best Regards, xunxun -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
2011/10/14 xunxun xunxun1...@gmail.com: Hi, Kai 于 2011/10/14 18:31, Kai Tietz 写道: Candian-cross compiler By the way, what is Candian-cross compiler ? This is the first time I heared it. -- Best Regards, xunxun See http://en.wikipedia.org/wiki/Cross_compiler#Canadian_Cross for more detailed information. Cheers, Kai -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
2011/10/14 xunxun xunxun1...@gmail.com 于 2011/10/14 18:23, Alexandre Gouraud 写道: windows native Now what compiler you use? see below. I am not sure I do (or want) canadian-cross compilation. I just need a win64 native compiler, and in the manual it is said I would need to start creating a cross compiler first. $ gcc -v Using built-in specs. COLLECT_GCC=C:\s2e\s2e-toolchain\mingw64\bin\gcc.exe COLLECT_LTO_WRAPPER=c:/s2e/s2e-toolchain/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: /home/drangon/work/mingw-w64-dgn/source/gcc/configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --disable-nls --enable-languages=c,c++,objc,obj-c++ --with-gmp=/home/drangon/work/mingw-w64-dgn/build/for_target --enable-twoprocess --disable-libstdcxx-pch --disable-win32-registry --prefix=/home/drangon/work/mingw-w64-dgn/target --with-sysroot=/home/drangon/work/mingw-w64-dgn/target Thread model: win32 gcc version 4.6.1 20110417 (prerelease) (GCC) -- Alexandre -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
On 10/14/2011 20:01, xunxun wrote: 于 2011/10/14 19:37, Alexandre Gouraud 写道: see below. I am not sure I do (or want) canadian-cross compilation. I just need a win64 native compiler, and in the manual it is said I would need to start creating a cross compiler first. No, you don't need cross compiler, because you have had a x86_64-w64-mingw32 native compiler. $ gcc -v Using built-in specs. COLLECT_GCC=C:\s2e\s2e-toolchain\mingw64\bin\gcc.exe COLLECT_LTO_WRAPPER=c:/s2e/s2e-toolchain/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: /home/drangon/work/mingw-w64-dgn/source/gcc/configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --disable-nls --enable-languages=c,c++,objc,obj-c++ --with-gmp=/home/drangon/work/mingw-w64-dgn/build/for_target --enable-twoprocess --disable-libstdcxx-pch --disable-win32-registry --prefix=/home/drangon/work/mingw-w64-dgn/target --with-sysroot=/home/drangon/work/mingw-w64-dgn/target Thread model: win32 gcc version 4.6.1 20110417 (prerelease) (GCC) If you native build the gcc, you can use --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 ps: drangon mingw64 gcc is built by jon_y. I thought they were built by tdm, which jon_y do you refer to? signature.asc Description: OpenPGP digital signature -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Building the cross win32 win64 compiler
It's my mistake. I thought this was built by you, but I don't think the edition's maintainer is TDM. On Fri, Oct 14, 2011 at 8:40 PM, JonY jo...@users.sourceforge.net wrote: On 10/14/2011 20:01, xunxun wrote: 于 2011/10/14 19:37, Alexandre Gouraud 写道: see below. I am not sure I do (or want) canadian-cross compilation. I just need a win64 native compiler, and in the manual it is said I would need to start creating a cross compiler first. No, you don't need cross compiler, because you have had a x86_64-w64-mingw32 native compiler. $ gcc -v Using built-in specs. COLLECT_GCC=C:\s2e\s2e-toolchain\mingw64\bin\gcc.exe COLLECT_LTO_WRAPPER=c:/s2e/s2e-toolchain/mingw64/bin/../libexec/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: /home/drangon/work/mingw-w64-dgn/source/gcc/configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --disable-nls --enable-languages=c,c++,objc,obj-c++ --with-gmp=/home/drangon/work/mingw-w64-dgn/build/for_target --enable-twoprocess --disable-libstdcxx-pch --disable-win32-registry --prefix=/home/drangon/work/mingw-w64-dgn/target --with-sysroot=/home/drangon/work/mingw-w64-dgn/target Thread model: win32 gcc version 4.6.1 20110417 (prerelease) (GCC) If you native build the gcc, you can use --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 ps: drangon mingw64 gcc is built by jon_y. I thought they were built by tdm, which jon_y do you refer to? -- Best Regards, xunxun -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
