On Thu, Jul 29, 2010 at 12:04 PM, Earnie <[email protected]> wrote: > > Misinformation abounds and we cannot keep up with what others say. For > instance from *-*-mingw32 the description adds "provides a subset of POSIX" > which is simply false. We have never proclaimed to provide a subset of > POSIX. We have proclaimed additions to the windows runtime to provide ANSI > C99 compliance. There may be a few POSIX items we've added to aid in > porting from POSIX to Windows API but only where there is a clear and > logical method in Windows already and those are few. >
Understood, but my link was to focus on the triplet, not their interpretation. <intentionally snip response as NightStrike answered part of those> > >> I appreciate all your comments. I can create a patch upstream for >> this if we agree on the outcome. > > Thanks for the offer for upstream patching but let's make sure everyone > agrees before patching anything. > > IMO, there should be only two triplets to identify MinGW (where MinGW is a > reference to both projects). The first part of the triplet identifies the > CPU and for Windows that will be either i?86 or x86_64 and is derived from > ``uname -m''. The second part of the triplet identifies the processor > ``uname -p'' which MSYS uname gives unknown but config.guess/config.sub can > modified to the more commonly know *-pc-*. The third part of the triplet > gives the kernel (or runtime) name ``uname -s'' and for MSYS this is where > MSYSTEM comes into play. Given this my opinion is that we should only have > i[3456]86-pc-mingw32 and x86_x64-pc-mingw64. Feel free to express your > opinions. > > I don't have a 64 bit windows machine to test on. What does uname -m give > for the value? > 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. The changes to implement just 'mingw' (without the 32) are extensive and could affect a lot of projects that are assuming mingw32. 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. Thank you. -- 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
