Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20010425161611.021bff70@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Wed, 25 Apr 2001 16:22:39 -0400
To:	"Shawn Carey" <smc AT questra DOT com>, <cygwin AT cygwin DOT com>
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: make-3.79.1: /bin/sh.exe: Command not found
In-Reply-To:	<005601c0cdbb$331a3d70$4c0b140a@ddns.roc.questra.com>
Mime-Version:	1.0

At 03:09 PM 4/25/2001, Shawn Carey wrote:
>Hello,
>
>I'm using cygwin's build of GNU make on a Windows 2000 system.  I recently
>upgraded the make executable from version 3.79 to 3.79.1, and now I'm having
>some problems...
>
>The compile-time initialization of "default_shell" (main.c:1134) has changed
>from "sh.exe" in version 3.79 to "/bin/sh.exe" in 3.79.1.  The unqualified
>value of "sh.exe" allowed make to find sh.exe using PATH, but "/bin/sh.exe"
>does not exist on my system and is not found by make.  The following
>Makefile demonstrates the problem I'm seeing:
>
>##### begin
>all:
>         echo "SHELL=$(SHELL) ($(origin SHELL))"
>##### end
>
>Here are the results when I execute this Makefile with make 3.79 and 3.79.1:
>
>C:\TEMP> make-3.79
>echo "SHELL=sh.exe (default)"
>SHELL=sh.exe (default)
>
>C:\TEMP> make-3.79.1
>echo "SHELL=/bin/sh.exe (default)"
>make-3.79.1: /bin/sh.exe: Command not found
>make-3.79.1: *** [all] Error 127
>
>Was this change intentional?  If so, is there some way to get my makefiles
>to run again without copying a shell to /bin or running make with
>"SHELL=sh.exe" on the command line?  Any help is greatly appreciated!



If you're asking this question here and you're using Cygwin as you claim,
then if you do not have /bin/sh.exe, your installation is non-standard.
Questions about non-standard installations, while occasionally entertained, 
are not really a concern of this list.

The reason sh.exe was changed to /bin/sh.exe was because there were problems
on allot of systems with sh.exe not being in the path in some circumstances.  
Changing it to /bin/sh.exe resolved that issue.  You can check the email 
archives for details on this if you like.

Sorry, I don't have any suggestions beyond those you mentioned.


Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -