On Thu, Jul 29, 2010 at 8:33 PM, JonY <[email protected]> wrote: > On 7/30/2010 05:59, Luis Lavena wrote: >> On Thu, Jul 29, 2010 at 4:57 PM, Earnie<[email protected]> wrote: >>> NightStrike wrote: >>>> On Thu, Jul 29, 2010 at 3:20 PM, Earnie<[email protected]> >>>> wrote: >>>> >>>>> NightStrike wrote: >>>>> >>>>>> On a long term scale, it'd be nice to compile msys natively for >>>>>> win64. That's a looooong way off, though. >>>>>> >>>>>> >>>>> I have no way to even begin to try it. First though one would need to >>>>> bootstrap GCC 64 bits with the MSYS runtime while at the same time >>>>> bootstrapping MSYS runtime into 64 bits. >>>>> >>>> I thought the first step was porting newlib. Doesn't msys still use that? >>>> >>> Yes, it uses newlib and a mix of Windows API calls. But newlib may >>> actually be the easier part to convert. >>> >> >> 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. What > if I wanted to run plain mingw.org GCC on win64? > > IMHO, setting MSYSTEM would be a better approach.
You could just use the already existent PROCESSOR_* variables that windows puts in the environment. They should contain everything you need. ------------------------------------------------------------------------------ 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
