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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Thu, 24 Feb 2000 14:33:09 -0500 Message-Id: <200002241933.OAA19171@envy.delorie.com> From: DJ Delorie To: gmoore AT openmarket DOT com CC: cygwin AT sourceware DOT cygnus DOT com In-reply-to: <38B58694.48478A1E@openmarket.com> (gmoore@openmarket.com) Subject: Re: rebuilding cywin v1.0: where is sh.exe References: <38B58694 DOT 48478A1E AT openmarket DOT com> > I've noticed that the Cygwin v1.0 that I just purchased behaves > somewhat differently than the version B20 that I was using > previously. It seems that Cygwin v1.0 was mounting the C:\Cygwin in > "binary" mode rather than "text!=binary" as did the Cygwin B20. Yup, this was on purpose. > OK so then I edit c:\Cygwin\src\bash\make_cmd.c and put in changes that I got > from this email list and then kicked off a full build. > cd c:\Cygwin > src\rebuild.bat Um, you do mean "./configure; make" right? > The make'ing of the "install" target failed because it couldn't find "sed". sed is on the CD and should be installed with everything else. > After the build I have no sh.exe under c:\build1. I do have a new > bash.exe but it is the sh.exe that I would like to use (I think) in > my makefiles as "SHELL=sh.exe". Anyone know if sh.exe is supposed > to get rebuilt and how it differs from bash.exe? sh.exe is from ash, not bash. If you want to rebuild sh.exe, you need to rebuild ash. However, you may choose to copy bash.exe to sh.exe. They both work, but ash is smaller and faster. However, ash may not need the bugfix you are applying. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com