X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Daniel Brockman Subject: Re: trouble with bash / if in recent release / update ? Date: Tue, 30 Jan 2007 06:53:50 +0000 (UTC) Lines: 49 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Tim Hanson faz.de> writes: > > hi, a colleague and i recently tried upgrading an existing cygwin and found that > basic bash script features broke. > [...] > > does this ring a bell for anyone? > > i'd be grateful for pointers. (or advice on how to provide more clues.) > > cheers, > > Tim > > You aren't alone, Tim. I have same problem. I updated last night. My sh (bourne shell) scripts didn't work this morning. I diff the bash.exe and sh.exe binaries and they are the same. I tried updating from a differnt mirror, but that didn't fix the problem. Workaround: I'm using zsh instead of sh . Back to the bugs ... `echo' command seems to work backwards! In a script... echo foo bar produces output ... bar foo A blank line in the script file produces err msg : command not found I can't figure out a way to make the new version of sh.exe work. Imho, it's broken. db -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/