From: Craig Hackney <craig@triscend.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: make 3.79.1-4 'make: /bin/sh.exe: Command not found' when running without sh.exe
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <2407239113CD914CBA855A47698F01B06220FA@SUGAH2.triscend.com> (raw)
There appears to be a problem with this version of make please
see below.
The ChangeLog.Cygnus file contains information on a change that
causes an error if sh.exe is not in /bin when make is run.
---------
* main.c (main): Avoid setting no_default_sh_exe to 0 in all cases.
Default to /bin/sh.exe on Cygwin. Lookup COMSPEC for --win32.
---------
The default shell is set to a unix style shell, ie. /bin/sh,
main.c contains code that checks the MAKE_MODE environment
variable see below..
---------
/* Read the environment variable MAKE_MODE */
/* If it's "UNIX", set unixy_shell to 1. If it's "WIN32" or
anything else, stay with the default of 0. */
make_mode_env = getenv ("MAKE_MODE");
if (make_mode_env && strcaseequ (make_mode_env, "UNIX"))
unixy_shell = 1;
---------
The above code checks to see if the MAKE_MODE is 'unix' and, if
it is sets unixy_shell (which is already set since the default
shell is now /bin/sh). Any other setting, i.e. WIN32, will use
the default, which is a unix shell. So make is looking for
/bin/sh even when MAKE_MODE is set to WIN32, the only workaround
is to specify --win32 as a command line option to make.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-11-16 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 8:26 Craig Hackney [this message]
2001-11-11 8:26 ` Christopher Faylor
2001-11-11 8:26 ` Christopher Faylor
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=2407239113CD914CBA855A47698F01B06220FA@SUGAH2.triscend.com \
--to=craig@triscend.com \
--cc=cygwin@cygwin.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.
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).