From: David G. <DGr...@am...> - 2011-10-19 15:51:14
|
Has anyone done this? I want to fix Ada so that I can update to 4.6.1, but I can't even build C. How was the recently-released MinGW 4.6.1 built? Is there documentation for the build environment that made it? Ada shouldn't be too much of a problem. TDM-GCC 4.6.1 has it working, so it shouldn't be too big a deal, I just need to get a working build environment. |
From: xunxun <xun...@gm...> - 2011-10-19 16:01:05
|
于 2011/10/19 23:50, David Gressett 写道: > Has anyone done this? I want to fix Ada so that I can update to 4.6.1, but I can't even build C. How was the recently-released MinGW 4.6.1 built? Is there documentation for the build environment that made it? > > Ada shouldn't be too much of a problem. TDM-GCC 4.6.1 has it working, so it shouldn't be too big a deal, I just need to get a working build environment. You should get pthreads-win32, libiconv, gmplib, mpfr, mpc, ppl, cloog before you build gcc4.6.1. If you want to know how TDM builds, you can get the build script from http://sourceforge.net/projects/tdm-gcc/files/Sources/TDM%20Sources/ -- Best Regards, xunxun |
From: Teemu N. <sti...@ya...> - 2011-10-19 16:48:50
|
On 19.10.2011 18:50, David Gressett wrote: > Ada shouldn't be too much of a problem. TDM-GCC 4.6.1 has it working, so it shouldn't be too big a deal, I just need to get a working build environment. Why don't you use TDM's build? |
From: David G. <DGr...@am...> - 2011-10-19 18:53:00
|
>> Ada shouldn't be too much of a problem. TDM-GCC 4.6.1 has it working, so it shouldn't be too big a deal, I just need to get a working build environment. >Why don't you use TDM's build? I want the MinGW gcc to have all of the pieces it should have, and I don't want to have to rebuild all of my Ada projects with a different compiler. Also, with the MinGW gcc, the people who build it are being picky about compliance with Microsoft software licenses, and I don't know how well TDM-gcc is handling that situation. I do know that the MinGW64 crowd is being sloppy. If Microsoft ever decides to drop a ton of legal bricks on license violators, MinGW gcc will be OK. The others will probably disappear. |
From: Teemu N. <sti...@ya...> - 2011-10-19 19:35:55
|
On 19.10.2011 21:52, David Gressett wrote: > >>> Ada shouldn't be too much of a problem. TDM-GCC 4.6.1 has it working, so it shouldn't be too big a deal, I just need to get a working build environment. > >> Why don't you use TDM's build? > > I want the MinGW gcc to have all of the pieces it should have, and I don't want to have to rebuild all of my Ada projects with a different compiler. Also, with the MinGW gcc, the people who build it are being picky about compliance with Microsoft software licenses, and I don't know how well TDM-gcc is handling that situation. I do know that the MinGW64 crowd is being sloppy. If Microsoft ever decides to drop a ton of legal bricks on license violators, MinGW gcc will be OK. The others will probably disappear. Ok, so follow the instructions on how to build GCC-4.6.1-2 for MinGW: http://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/GCC/Version4/gcc-4.6.1-2/ Before starting pkgbuild apply gcc/buildsys.patch and gcc/g-socthi-mingw.patch from TDM's sources: http://sourceforge.net/projects/tdm-gcc/files/Sources/TDM%20Sources/gcc-4.6.1-tdmsrc-2.zip/download |
From: Teemu N. <sti...@ya...> - 2011-10-19 19:39:47
|
One addition to my instructions, edit pkgbuild.ini so that: --enable-languages=c,c++,fortran,objc,obj-c++ becomes --enable-languages=c,c++,fortran,objc,obj-c++,ada |
From: John E. / T. <td...@td...> - 2011-10-20 00:15:45
|
On 10/19/2011 12:52 PM, David Gressett wrote: > Also, with the MinGW gcc, the people who build it are being picky about compliance with Microsoft software licenses, and I don't know how well TDM-gcc is handling that situation. I do know that the MinGW64 crowd is being sloppy. If Microsoft ever decides to drop a ton of legal bricks on license violators, MinGW gcc will be OK. The others will probably disappear. The 32-bit edition of TDM-GCC is no more and no less than a drop-in replacement for MinGW's GCC packages, and is based entirely on GPL(+exception) and LGPL code. (This can be easily discerned from the README.) The mingwrt and w32api packages, whence any concerns about Microsoft licensing would stem, must come from the MinGW project. Your objection to rebuilding all your projects with a different compiler is certainly valid, particularly since TDM-GCC's default distribution has two ABI incompatibilities with MinGW's -- its SJLJ exception model (vs. MinGW's DW2), and its use of a "fully dynamic" std::string class (necessary when using static libstdc++ and DLLs). Cheers, John E. / TDM |