From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: jarekczek@poczta.onet.pl, emacs-devel@gnu.org
Subject: Re: Bootstrap failure on MS-Windows
Date: Sat, 09 Nov 2013 17:18:24 +0200 [thread overview]
Message-ID: <83eh6p4n9b.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0gsH40n5rwXE6_imvPwPNEqdXWvjsvGddh5y-XWTb=5xA@mail.gmail.com>
> Date: Sat, 9 Nov 2013 15:33:55 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Jarek Czekalski <jarekczek@poczta.onet.pl>,
> Emacs development discussions <emacs-devel@gnu.org>
>
> >> 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.
>
> If you refer to the patch I sent [1], the reading of
> 'nt/mingw-cfg.site' from the configure script is conditioned to the
> MSYS environment. So, with that approach, we still need a way of
> checking whether the shell is running on a MSYS environment.
'uname' is invoked by config.guess, so if the value it returns is
needed, it is already available to the configure script in the form of
'opsys' variable, albeit somewhat later than where you wanted to read
the site-config file.
Relying on a raw 'uname' is IMO wrong, because it would preclude
setting --host etc. from the configure command-line args.
next prev parent reply other threads:[~2013-11-09 15:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 18:04 Bootstrap failure on MS-Windows Dani Moncayo
2013-11-02 18:52 ` Glenn Morris
2013-11-05 8:24 ` Glenn Morris
2013-11-05 18:14 ` Dani Moncayo
2013-11-05 18:26 ` Eli Zaretskii
2013-11-05 19:46 ` Dani Moncayo
2013-11-05 20:05 ` Eli Zaretskii
2013-11-05 21:08 ` Dani Moncayo
2013-11-05 21:52 ` Glenn Morris
2013-11-06 15:38 ` Dani Moncayo
2013-11-06 20:32 ` Glenn Morris
2013-11-06 20:50 ` Eli Zaretskii
2013-11-06 20:55 ` Glenn Morris
2013-11-12 2:42 ` Glenn Morris
2013-11-06 0:27 ` Óscar Fuentes
2013-11-06 1:35 ` Glenn Morris
2013-11-06 1:42 ` Glenn Morris
2013-11-06 13:59 ` Andy Moreton
2013-11-06 17:08 ` Eli Zaretskii
2013-11-06 20:24 ` Andy Moreton
2013-11-08 10:32 ` Andy Moreton
2013-11-08 11:02 ` Eli Zaretskii
2013-11-08 13:34 ` Andy Moreton
2013-11-08 14:18 ` Eli Zaretskii
2013-11-09 12:36 ` Andy Moreton
2013-11-09 13:19 ` Eli Zaretskii
2013-11-10 21:21 ` Andy Moreton
2013-11-09 13:24 ` Jarek Czekalski
2013-11-09 13:51 ` Eli Zaretskii
2013-11-09 14:33 ` Dani Moncayo
2013-11-09 15:18 ` Eli Zaretskii [this message]
2013-11-05 20:29 ` Glenn Morris
2013-11-05 21:09 ` Dani Moncayo
2013-11-05 20:29 ` Glenn Morris
2013-11-05 18:27 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eh6p4n9b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jarekczek@poczta.onet.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).