sh.exe: Command not found

[Neil Bradley]

> >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.
> Ok.  But that puts a certain burden on you to support it, then.  It's
> difficult to provide help for people who have renamed things and moved
> them around to non-standard locations.

I understand. I'm supposed to be the buildmeister for the project, and I
fully accept all responsibility therein. I've also done a bit of homework
and footwork to make sure that I wasn't doing something plainly obvious,
as I know how irritating it is to deal with a complete moron who just asks
questions without doing any investigation. But I'm also sure you know how
hard is to get software engineers to change their ways even in the
slightest (I being one of them!). ;-(

> >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. 
> 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.

Yep - that did it - that is, providing SHELL= on the make command line.  
A heartfelt thank you to Chris & Mumit!

Now, where can I get rm.exe? ;-)

-->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