From: Jason Rumney <jasonr@gnu.org>
Cc: Guy Gascoigne-Piggford <guy@wyrdrune.com>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: NT mingw/msys build problem
Date: Wed, 27 Oct 2004 11:43:12 +0100 [thread overview]
Message-ID: <417F7BC0.7060208@gnu.org> (raw)
In-Reply-To: <00ab01c4bc0a$b0c87ac0$0200a8c0@sedrcw11488>
Lennart Borgman wrote:
>I do not know how make works, but I can't avoid the hang when MSYS sh.exe is
>in the path. The hang is caused by $(shell echo) in the make file. This does
>not return since it runs "cmd echo" and that starts a new shell without
>doing "echo". Actually it is bad syntax. The syntax for cmd is
>
> CMD [/X | /Y] [/A | /U] [/Q] [[/C | /K] string]
>
>You have to supply /C or /K for the string command to be carried out. (At
>least this is the syntax on NT4 and I believe it has not changed.)
>
>
>
The $(shell COMMAND) macro should provide the correct arguments. That is
the way cygwin and mingw32 make work, msys seems to be the only broken
one in this regard.
>I do not understand why the test is made. It seems like make has found sh
>already but it still wonders something about "shell". Why does make do that?
>
>
Make should know the shell already, but the Emacs makefiles do not. They
need to do that test to find out.
>So at the moment there is actually no other way to build Emacs on ms windows
>than using Cygwin as far as I can see.
>
I use mingw and cmd.exe. The key is to stay clear of msys.
next prev parent reply other threads:[~2004-10-27 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 8:28 NT mingw/msys build problem Guy Gascoigne-Piggford
2004-10-25 9:15 ` Jason Rumney
2004-10-25 22:41 ` Guy Gascoigne-Piggford
2004-10-25 23:09 ` Jason Rumney
2004-10-27 9:50 ` Lennart Borgman
2004-10-27 10:21 ` Lennart Borgman
2004-10-27 10:43 ` Jason Rumney [this message]
2004-10-27 19:16 ` Lennart Borgman
2004-10-25 16:00 ` Lennart Borgman
2004-10-26 18:11 ` Guy Gascoigne - Piggford
-- strict thread matches above, loose matches on Subject: below --
2004-10-26 1:07 Fred Kunz
2004-10-26 1:15 Fred Kunz
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=417F7BC0.7060208@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=guy@wyrdrune.com \
/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.