On 7/28/2010 07:13, Luis Lavena wrote: > Hello, > > At this time I'm using TDM64 provided 4.5.0 binaries, but before > (using the 32-to-64 compiler) found the same issue. > > Using the standard config.guess (and sub) both 32bits and 64bits are > identified as "i686-pc-mingw32" > > I heard that before mingw64 gained it's own identification, but using > the files from config.git: > > http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD > http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD > > Still showed i686-pc-mingw32 > > Should I be using a customized config.guess? What I would like to do > is properly detect it (natively) or patch some libraries that include > config.guess files. > > Thank you for your time and looking forward suggestions.
Hi, just use --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 and you should be fine. MSYS has been strongly associated with mingw.org for a very long time, hence to autotools, MSYS uname string can be assumed to be i686-pc-mingw32. ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
