FYI, i use tdm-gcc on windows/amd64, normal mingw gcc on windows/386.
On Aug 11, 2014 1:24 AM, "Andrew Gerrand" <a...@google.com> wrote:
> On 11 August 2014 15:21, minux <mi...@golang.org> wrote:
>> FYI, i use tdm-gcc on windows/amd64, normal mingw gcc on windows/386.
i think it's because of historical reasons.
i only know about mingw at first, but i couldn't find a working 64-bit binary release, so i found and switched to tdm, and it works well.
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
(Also now seeking confirmation from Windows contributors that there's nothing inherently wrong with TDM-GCC. It seems mostly a matter of packaging, to me.)
On Monday, August 11, 2014 12:17:56 AM UTC-5, Andrew Gerrand wrote:(Also now seeking confirmation from Windows contributors that there's nothing inherently wrong with TDM-GCC. It seems mostly a matter of packaging, to me.)It would be awesome if Google built the MinGW-w64 binaries and hosted it -- especially given what Ken Thompson taught us about compiler backdoors.TDM-GCC hasn't been updated in a while. If I'm not mistaken, TDM-GCC uses MinGW-w64 which is frequently updated. It might be better to go directly to the original.