On Thu, Jul 29, 2010 at 9:33 PM, JonY <[email protected]> wrote: > On 7/30/2010 05:59, Luis Lavena wrote: >> >> Earnie: where specifically is uname source code? I can take a look to >> Windows API and since I have a x64 OS can check different results and >> let you know. >> >> If I can add proper identification of x86_64 (based from the OS it is >> running) will make me feel better for making you guys waste all this >> time answering this thread. >> > > Hi, > > I think its a bad idea to jump to conclusions based on OS running.
I think get it identified is way better than 'unknown' > What if I > wanted to run plain mingw.org GCC on win64? > > IMHO, setting MSYSTEM would be a better approach. You mean force compilation to something that is not the native one? --host will still be available. I'm fine with both approaches as long makes more easy for people using mingw-w64 to generate Windows x64 binaries as for people using mingw.org binaries to generate 32bits binaries. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry ------------------------------------------------------------------------------ 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://p.sf.net/sfu/dev2dev-palm _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
