[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bootstrap failure on MS-Windows
From: |
Eli Zaretskii |
Subject: |
Re: Bootstrap failure on MS-Windows |
Date: |
Sat, 09 Nov 2013 15:51:12 +0200 |
> Date: Sat, 09 Nov 2013 14:24:21 +0100
> From: Jarek Czekalski <address@hidden>
>
> Maybe "uname" could be an option to detect mingw? On my system it
> returns "windows32" for non-login, and "MINGW32_NT-6.1" for --login
> shell. Cygwin returns CYGWIN_NT-6.1-WOW64, so it won't be mistaken as mingw.
Thanks, but I believe the need for this will be eliminated, once the
change that makes configure read mingw-cfg.site directly is committed.
- Re: Bootstrap failure on MS-Windows, (continued)
- Re: Bootstrap failure on MS-Windows, Eli Zaretskii, 2013/11/06
- Re: Bootstrap failure on MS-Windows, Andy Moreton, 2013/11/06
- Re: Bootstrap failure on MS-Windows, Andy Moreton, 2013/11/08
- Re: Bootstrap failure on MS-Windows, Eli Zaretskii, 2013/11/08
- Re: Bootstrap failure on MS-Windows, Andy Moreton, 2013/11/08
- Re: Bootstrap failure on MS-Windows, Eli Zaretskii, 2013/11/08
- Re: Bootstrap failure on MS-Windows, Andy Moreton, 2013/11/09
- Re: Bootstrap failure on MS-Windows, Eli Zaretskii, 2013/11/09
- Re: Bootstrap failure on MS-Windows, Andy Moreton, 2013/11/10
- Re: Bootstrap failure on MS-Windows, Jarek Czekalski, 2013/11/09
- Re: Bootstrap failure on MS-Windows,
Eli Zaretskii <=
- Re: Bootstrap failure on MS-Windows, Dani Moncayo, 2013/11/09
- Re: Bootstrap failure on MS-Windows, Eli Zaretskii, 2013/11/09
- Re: Bootstrap failure on MS-Windows, Glenn Morris, 2013/11/05
- Re: Bootstrap failure on MS-Windows, Dani Moncayo, 2013/11/05
- Re: Bootstrap failure on MS-Windows, Glenn Morris, 2013/11/05
- Re: Bootstrap failure on MS-Windows, Glenn Morris, 2013/11/05