On Thu, Jul 29, 2010 at 11:44 AM, Luis Lavena <[email protected]> wrote: > Windows 7 x64, using cmd.exe in 64bits mode (doesn't matter as sh is > 32bits and triggers WOW) > > C:\Users\Luis>sh -c "uname -m" > i686 > > C:\Users\Luis>sh -c "uname -p" > unknown > > C:\Users\Luis>sh -c "uname -s" > MINGW32_NT-6.1 > > I think, at this time, with such wide spread and usage of 'mingw32' > moniker, killing it will only bring grief and problems to you guys > that I would like to avoid. > > @NightStrike: 'windows' sounds good, but as mentioned above, will be > almost impossible to bring this now.
I can dream, can't I? :) > The changes to implement just 'mingw' (without the 32) are extensive > and could affect a lot of projects that are assuming mingw32. Actually, going from mingw32 to mingw is fairly easy. config.guess has already been modified upstream to be mingw*. So actually, I had an item on my todo list to make all of our automated builds drop the -32. Of course, that has taken a lesser priority than making the automated builds actually work............ > With all due respect, back to my point: has anyone tried send patches > to upstream for config.guess? I would like to as correct platform > detection can remove one additional step users need to do manually > every time. I thought we already straightened out upstream config.guess. The issue is in the uname command issued in a WOW environment, IIUC. On a long term scale, it'd be nice to compile msys natively for win64. That's a looooong way off, though. ------------------------------------------------------------------------------ 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
