Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 21 Feb 2001 20:17:07 -0800 (PST) From: Neil Bradley To: cygwin AT cygwin DOT com Subject: Re: sh.exe: Command not found In-Reply-To: <20010221223819.A8880@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > >> >gmake[1]: Leaving directory `/cygdrive/d/work' > >> >gmake: *** [Boot\\boot.lib] Error 2 > >> Why not use the version of make that comes with Cygwin? > >It is, actually. I change it to "gmake" so it doesn't conflict with > >another project that uses "make", and they need to coexist on the same > >system. > Well, you have both renamed it and moved it to a nonstandard location. Correct. Does renaming it actually harm things? I'd rather not have to require >30 developers to install the entire cygwin package - we're trying to keep it easily movable from one machine to another. > I wonder if that is your problem. Usually sh.exe is expected to be in > the standard /bin location. Does /bin/sh.exe exist? It doesn't. Is /bin something that should be created and stored on whatever drive it's in? It'd be nice if I could set some environment variable that would point it to the proper location. But strangely, why would a invocation of a command that uses quotes cause a different behavior than that of a compile? -->Neil ------------------------------------------------------------------------------- Neil Bradley Mechanical engineers build weapons. Civil engineers Synthcom Systems, Inc. build targets. ICQ #29402898 -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple