MinGW 和常规 GCC 之间的区别？
在 MinGW 的 SourceForge 页面上，您可以下载 GCC 4.5.2，这是最新版本。在 GNU 镜像上，您可以下载 GCC 4.6 源代码，并使用可能的 Windows 目标之一对其进行编译：
i[3456789]86-w64-mingw*
i[3456789]86-*-mingw*
x86_64-*-mingw*
Is there a Difference between using one of those Targets 和传统的 GCC for MinGW?使用常规 GCC 是否有意义，因为它有更多最新版本，或者等到 MinGW 的最新 GCC 发布更有意义？
On the SourceForge page for MinGW, you can download the GCC 4.5.2 and that's the latest version. On the GNU mirrors, you can download the GCC 4.6 source and compile it with one of the possible windows targets:
i[3456789]86-w64-mingw*
i[3456789]86-*-mingw*
x86_64-*-mingw*
Is there a difference between using one of these targets and the traditional GCC for MinGW? Would it make sense to use the regular GCC because it has more up-to-date versions or would it make more sense to wait until an up-to-date GCC for MinGW is released?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
正如您在 SourceForge 上的 GCC MinGW 版本附带的 README 文件中看到的那样，没有使用本地补丁，而且我认为这种情况已经有一段时间了，所以假设 GCC 代码库中没有需要新补丁的更改本地补丁，您可以很好地从其中一个镜像下载 GCC 源代码并自己构建它们。
我自己过去也这样做过，特别是因为我使用 gfortran，它正在大量开发中，所以我时不时地拍摄最新的快照并自己构建它，这样我就可以使用最近才引入的某些新功能。
（我不得不承认，我花了一些时间来尝试让构建没有错误地运行，并且在没有出现问题的一段时间后，我最近遇到了一些我无法完全解决的新问题。我很快就必须再试一次。 ）
As you can see in the README file accompanying the MinGW release of GCC on SourceForge, no local patches were used, and I think this has been the case for quite a while now, so assuming there were no changes in the GCC codebase that require new local patches, you can very well download the GCC sources from one of the mirrors and build them yourself.
I have done so myself in the past, especially because I use gfortran, which is under quite heavy development, so from time to time I take the most recent snapshot and build that myself, so I can use certain new features that were only recently introduced.
(I have to admit that it took some trying to get the build to run without errors, and after a period without problems, I recently ran into some new ones that I couldn't completely smooth out. I will have to try again soon.)