On Thu, Sep 9, 2010 at 11:11 AM, JonY <[email protected]> wrote: >> Can this be fixed and lib64 directory be removed? >> > If you have moved them and lib64 becomes empty, yes.
Move them to lib, right? What are the use of those files? >> Another thing, typically other MinGW-w64 binaries for Windows >> will have gcc along with x86_64-w64-mingw32-gcc.exe and other >> similar links. But the automatic build does not have that. >> > > You should not be using "gcc", but x86_64-w64-mingw32-gcc instead. > It is a cross compiler. I see. This makes sense. However, TDM64 does use "gcc", under 32bit or 64bit Windows. I think it is a cross-compiler as well. >> One good thing is that mingw_i686 version is now provided >> (mingw-w64-1.0-bin_i686-mingw_20100906.zip). Thanks. Just >> wondering if it is better to have a 64bit Windows build as well >> (like http://www.drangon.org/mingw/ ). 64bit Linux build is >> provided along with 32bit Linux. >> > > I don't know about 64bit windows builds, but there is no benefit from using > 64bit compilers, unless you need more than 4GB to process your sources. > > Its a low priority for now, we really lack manpower. No problem. I am just wondering about why there is a 64bit Linux build but no 64bit Windows build. I use both Windows and Linux, MinGW and Cygwin. But I just think Windows should have higher priority than Linux for MinGW-w64. Now I understand the situation. It is not a real problem. -- Xiaofan ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
