From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: vincent.b.1@hotmail.fr, eggert@cs.ucla.edu, emacs-devel@gnu.org,
dmoncayo@gmail.com
Subject: Re: Latest EMACS on BZR trunk does not compile with MinGW
Date: Thu, 05 Jun 2014 09:31:50 -0400 [thread overview]
Message-ID: <jwvzjhrze4y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <834n006pcg.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 05 Jun 2014 05:51:27 +0300")
>> How 'bout testing a functionality on which we rely during the build,
>> rather than looking for some indirect evidence?
> Chicken-and-egg problem: that test is there so that we could source
> nt/mingw-cfg.site file, which does what you want.
AFAIK it's not exactly a chicken-and-egg problem: yes, we usually rely
on autoconf to do "functionality tests" and here we'd need to do
a functionality test in order to decide how to run autoconf, but we can
perform functionality tests without autoconf.
One more thing: what is this test *really* trying to figure out?
You say that the "uname" output is not very useful, but I don't
understand why
case "$(uname -a)" in
*MINGW* | *MinGW* ) ...
esac
wouldn't give the right answer. IIUC we're trying to figure out whether
we're doing an "MSYS" build (whatever that means) and to do that we
should:
- discover that we're on a w32 system.
- discover that we're not doing a cygwin build.
Stefan
next prev parent reply other threads:[~2014-06-05 13:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 20:00 Latest EMACS on BZR trunk does not compile with MinGW Vincent Belaïche
2014-06-03 20:22 ` Paul Eggert
2014-06-03 20:56 ` Óscar Fuentes
2014-06-03 21:15 ` Eli Zaretskii
2014-06-03 21:21 ` Vincent Belaïche
2014-06-04 6:47 ` Eli Zaretskii
2014-06-04 13:17 ` Vincent Belaïche
2014-06-04 13:31 ` Eli Zaretskii
2014-06-04 15:28 ` Vincent Belaïche
2014-06-04 15:44 ` Eli Zaretskii
2014-06-04 15:54 ` Dani Moncayo
2014-06-04 16:05 ` Eli Zaretskii
2014-06-04 21:50 ` Dani Moncayo
2014-06-05 0:42 ` Stefan Monnier
2014-06-05 2:51 ` Eli Zaretskii
2014-06-05 3:40 ` Óscar Fuentes
2014-06-05 7:03 ` Dani Moncayo
2014-06-05 9:03 ` Vincent Belaïche
2014-06-05 15:09 ` Eli Zaretskii
2014-06-05 14:51 ` Eli Zaretskii
2014-06-05 16:19 ` Óscar Fuentes
2014-06-05 17:52 ` Eli Zaretskii
2014-06-05 13:31 ` Stefan Monnier [this message]
2014-06-05 15:15 ` Eli Zaretskii
2014-06-05 16:50 ` Stefan Monnier
2014-06-05 18:07 ` Eli Zaretskii
2014-06-05 19:35 ` Paul Eggert
2014-06-05 19:54 ` Eli Zaretskii
2014-06-10 19:25 ` Dani Moncayo
2014-06-10 20:21 ` Eli Zaretskii
2014-06-05 20:54 ` Stefan Monnier
2014-06-05 2:47 ` Eli Zaretskii
2014-06-04 12:22 ` Using Qunsupported__w32_dialog Dmitry Antipov
2014-06-04 13:09 ` Eli Zaretskii
2014-06-04 13:37 ` Dmitry Antipov
2014-06-04 13:47 ` Eli Zaretskii
2014-06-04 14:06 ` Eli Zaretskii
2014-06-03 21:14 ` Latest EMACS on BZR trunk does not compile with MinGW Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvzjhrze4y.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dmoncayo@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=vincent.b.1@hotmail.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.