From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12955@debbugs.gnu.org
Subject: bug#12955: 24.3.50; Build process on MS-Windows: sometimes needs "human intervention"
Date: Thu, 22 Nov 2012 08:19:18 +0100 [thread overview]
Message-ID: <CAH8Pv0gUk8qZVziB0vEd=ab0pK5pJkZtsnkUqLXOMumZYQQwQA@mail.gmail.com> (raw)
In-Reply-To: <83a9uauwwo.fsf@gnu.org>
> Sorry, I don't want to do this. This might work now, but it does so
> by pure luck, and might break in some future version of cmd, because
> there _should_ be a space between /c and the command that follows.
Is that documented somewhere? I've read the help of "cmd" and I don't see it.
> The solution to this is simple: don't involve MSYS in building the
> native port of Emacs. It boils down to removing MSYS from PATH in the
> shell window where you run the build scripts.
That it one possible solution, but certainly not the one I'd like to
pick up, because it imposes an unnecessary restriction on the way of
building Emacs, and this particular restriction annoys me, because
Emacs can be build on Windows using the bash sell, and I like to do
so. The only problem I've observed when doing it is the one explained
in this thread, and I'd like to fix it.
In the (unlikely) event that a future version of cmd.exe gives
problems when invoked that way, we could find a solution for it, but I
doubt it will ever happen.
--
Dani Moncayo
next prev parent reply other threads:[~2012-11-22 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 20:49 bug#12955: 24.3.50; Build process on MS-Windows: sometimes needs "human intervention" Dani Moncayo
2012-11-21 22:43 ` Dani Moncayo
2012-11-22 3:41 ` Eli Zaretskii
2012-11-22 7:19 ` Dani Moncayo [this message]
2012-11-22 17:05 ` Eli Zaretskii
2012-11-22 19:16 ` Dani Moncayo
2012-11-23 8:53 ` Eli Zaretskii
2012-11-23 19:55 ` Dani Moncayo
2012-11-23 21:43 ` 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='CAH8Pv0gUk8qZVziB0vEd=ab0pK5pJkZtsnkUqLXOMumZYQQwQA@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=12955@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.