From: Eli Zaretskii <eliz@gnu.org>
To: Du Yanning <duyanning@gmail.com>
Cc: 11402@debbugs.gnu.org
Subject: bug#11402: Problem while compiling emacs-24.0.96 using MinGW on Win7
Date: Fri, 04 May 2012 13:30:15 +0300 [thread overview]
Message-ID: <834nrw6xxk.fsf@gnu.org> (raw)
In-Reply-To: <CALr_ej24_EX2NevXNU5YfCksOqdx=3C7xvtNXh2SFVX5X4xvpw@mail.gmail.com>
> Date: Fri, 4 May 2012 17:37:44 +0800
> From: Du Yanning <duyanning@gmail.com>
[Please keep the bug address on the CC list, so that this discussion
is logged by the bug tracker.]
> After I renamed MSYS sh.exe to aaash.exe and ran make, it said:
>
> F:\build-emacs\emacs-24.0.96\nt>make
> make: /bin/sh: Command not found
> make: /bin/sh: Command not found
> Using /bin/sh as shell.
> mkdir "oo-spd"
> make: /bin/sh: Command not found
> make: [oo-spd] Error 127 (ignored)
> mkdir "oo-spd/i386"
> make: /bin/sh: Command not found
> make: [stamp_BLD] Error 127 (ignored)
> echo oo-spd/i386 > stamp_BLD
> make: /bin/sh: Command not found
> make: *** [stamp_BLD] Error 127
>
> It seems that make need sh.exe.
> How can I correct it?
My crystal ball says your 'make' is an MSYS 'make'. If so, install
the MinGW 'make' instead, it can work without sh.exe. (You will
probably need MinGW or GnuWin32 ports of cp, rm and mv as well, they
are part of the Coreutils package.)
In general, when building Emacs, it is much better to remove MSYS from
Path, because MSYS tools are generally intended to be run only as part
of configuring and building Unix and GNU/Linux packages. By contrast,
the Windows port of Emacs should be built using native Windows tools.
next prev parent reply other threads:[~2012-05-04 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 7:34 bug#11402: Problem while compiling emacs-24.0.96 using MinGW on Win7 Du Yanning
2012-05-04 9:21 ` Eli Zaretskii
[not found] ` <CALr_ej24_EX2NevXNU5YfCksOqdx=3C7xvtNXh2SFVX5X4xvpw@mail.gmail.com>
2012-05-04 10:30 ` Eli Zaretskii [this message]
2012-05-04 13:43 ` Du Yanning
2012-05-04 14:21 ` 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
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=834nrw6xxk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11402@debbugs.gnu.org \
--cc=duyanning@gmail.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 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).