Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: cygwin
Compiler: gcc-4
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -DRECYCLES_PIDS -I.
-I/usr/src/bash-4.1.10-4/src/bash-4.1
-I/usr/src/bash-4.1.10-4/src/bash-4.1/include
-I/usr/src/bash-4.1.10-4/src/bash-4.1/lib -I/usr/include/ncursesw -g
-O2 -pipe
uname output: CYGWIN_NT-6.1 dell-3p5mzm1 1.7.9(0.237/5/3) 2011-03-29
10:10 i686 Cygwin
Machine Type: i686-pc-cygwin
Bash Version: 4.1
Patch Level: 10
Release Status: release
Description:
When I attempt to execute a bash script with DOS line endings, I
get
numerous errors concerning the \r at the end of each line.
This was not always true. When I first started to regularly use
cygwin in 2003 we had numerous bash scripts, with DOS line
endings,
that we used to maintain our product. When I returned to the
same
employer in 2009, having been laid off in 2007, and got the
latest
distribution of cygwin, I was surprised that none of our old
scripts
worked until I went through and converted to unix line endings.
I thought this must surely be a simple goof that would be fixed
in the
next release, but when I reloaded cygwin for my new PC late last
year
the bug was still there.
Repeat-By:
Take any working bash script file, pass through unixtodos (or
edit with
vi/vim/gvim, set fileformat=dos, and write out), and attempt to
run.
