Tim Hanson wrote:
hi, a colleague and i recently tried upgrading an existing cygwin and found that basic bash script features broke. he later went back to a working copy, tested and discovered that the features worked, upgraded again and confirmed that they were broken again. i've searched for hints that others have had this problem and haven't found any. the symptoms are pretty easy to test.in an interactive bash shell one can conform that these two if statements work: if [[ -z "17" ]]; then echo "ja"; else echo "ne"; fi ne if [[ -z "" ]]; then echo "ja"; else echo "ne"; fi ja if one then builds a bash script consisting only of #!/usr/bin/bash and this if statement (broken into separate lines) it fails along these lines: $ test.bash : command not test.bash: line 9: /usr/local/bin/test.bash: line 10: syntax error in conditional expression 'usr/local/bin/test.bash: line 10: syntax error near `]] 'usr/local/bin/test.bash: line 10: `if [[ -z "$1" ]] does this ring a bell for anyone? i'd be grateful for pointers. (or advice on how to provide more clues.)
Your line-endings are CRNLs. The best thing to do is to run d2u on the scripts in question. Read any recent Cygwin bash announcements for other options to resolve this situation and further details. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/
