On Thu, Mar 24, 2011 at 5:13 PM, Suresh Govindachar <sgovindac...@yahoo.com> wrote: > Hello, > > [Sending this from a new system; hope it appears in plain text.]
It did. > On a new Windows 7 64 bit laptop with > mingw-w64-1.0-bin_i686-mingw_20110318.zip and an old msys > copied from my XP 32 bit laptop, the command > > find /c/opt/msys /c/opt/mingw -name "*gcc*exe" | xargs ls -laF > > shows 4 matches: > > 1) [...] 726920 Mar 18 12:56 > /c/opt/mingw/bin/x86_64-w64-mingw32-gcc-4.5.3.exe > 2) [...] 726920 Mar 18 12:56 /c/opt/mingw/bin/x86_64-w64-mingw32-gcc.exe > 3) [...] 726920 Mar 18 12:56 /c/opt/mingw/mingw/bin/gcc.exe > 4) [...] 726920 Mar 18 12:56 /c/opt/mingw/x86_64-w64-mingw32/bin/gcc.exe > > For "gcc.exe --version", all 4 gcc.exe report: > > (GCC) 4.5.3 20110318 (prerelease) > > What is the purpose of each of the 4 gcc.exes -- what are they > to be used for? The binaries in /c/opt/mingw/bin/ are the ones you should use. The others are for internal use. The binary in the above directory with the extra version information (4.5.3) in the name is just there for convenience purposes if you need to select a GCC by specific version. Imagine a system where you have many compilers in your PATH, and you want to pick the right one. The mingw/ and x86_64-w64-mingw32/ directories are identical. > I am aware that the 32 bit mingw offers two > sets of compilers, one for building native windows > applications and the other for building "MSYS" applications > (applications that only run in a terminal that was somehow > tied to MSYS) -- is there something similar for mingw-w64? We do not offer compilers that target msys. That would imply that the resulting binaries would be linked against the msys dll. However, you can use our compilers within msys to generate native windows applications that are not linked against the msys dll. > My main use will be for building 64 bit gvim and perl modules > (for the 64 bit perl offered by Active State). > > Also, what does the "32" in mingw32 signify? Even though > mingw-w64-1.0-bin_i686-mingw_20110318.zip runs on 64 bit > Windows and is for building 64 bit Windows applications, it is > in itself a 32 bit windows application? The 32 signifies the Win32 API, which is still relevant for Win64 territory. It is essentially not needed anymore, and any triplet tests should check for -mingw*, not -mingw32. The particular file you cite actually runs on 32-bit windows (that's the i686-mingw part). It just so happens to be the case that 64-bit windows can run 32-bit windows binaries rather seamlessly. ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
