Re: Latest EMACS on BZR trunk does not compile with MinGW

[Dani Moncayo]

>> For example, wouldn't it be possible to check the output of 'uname'?
>
> Maybe, but it's not simple, because there's more than one kind
> available out there.  I have 3 on my system, and they report,
> respectively:
>
>   MINGW32_NT-5.1 HOME-C4E4A596F7 1.0.17(0.48/3/2) 2011-04-24 23:39 i686 Msys
>   MINGW32_NT-5.1 HOME-C4E4A596F7 1.0.12(0.46/3/2) 2012-07-05 14:56 i686 
> unknown
>   windows32 home-c4e4a596f7 2.5.1 2600 i686-pc Intel unknown MinGW
>
> In a nutshell, most of what a ported 'uname' reports is hard-wired
> into it when it is built, because there's no such OS as "MinGW".
> That's hardly a good way of reliably identifying MinGW.

I see.  Too bad that different MSYS flavors are not consistent
wrt the output of 'uname'.

Another option would be, perphaps, to check the environment
variable $OSTYPE (instead of $MSYSTEM).  I've just done a quick
test on my system: if I invoke "bash.exe" (without "--login"), I
see that $OSTYPE holds "msys", while $MSYSTEM is undefined.  (But
I don't know if this is also true in other MSYS flavors).

-- 
Dani Moncayo