Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 21 Feb 2001 23:37:31 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: sh.exe: Command not found Message-ID: <20010221233731.B9086@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010221231845.A9086@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Wed, Feb 21, 2001 at 10:25:02PM -0600 On Wed, Feb 21, 2001 at 10:25:02PM -0600, Mumit Khan wrote: >On Wed, 21 Feb 2001, Christopher Faylor wrote: > >> Mumit has clarified things in this regard. I'd forgotten that make would >> look for sh.exe in the path. I don't know why this isn't working for >> you. Possibly setting the SHELL environment variable or passing a SHELL= >> command line argument will work, as Mumit suggested. > >You can pass SHELL as a variable either on the command line as I had >shown, or in the makefile itself, but never taken from the environment. >Make by design ignores SHELL environment variable, given that it causes >very weird errors when users have say csh as the SHELL variable. Hmm. I thought the Cygwin code had a fallback to the SHELL environment variable but I just checked and that is not the case. Make does find sh.exe in the PATH, though, as you said. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple