Similar Bash 3.1.18 CR/LF Problem
Fri Sep 29 02:59:00 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
*There is NO bash 3.1.18* - just 3.1.17 release 8
According to Wilks, Dan on 9/28/2006 11:30 AM:
> Apologies that this is being written the day after without real output.
> I'm now at my desk without easy access to the machine in question.
> We've been using Cygwin with text-mode mounts for a long time without
> any problems. A new engineer started the other day, installed a
> brand-spanking-new cygwin and came to me with problems running a build.
> Without going into details of the build system, after a few hours I
> discovered that (all examples are from a cmd shell), foo.sh contains the
> single line "date; date<cr><lf>"
> C:> cd temp
> C:\temp> sh foo.sh -- works
> C:\temp> sh C:/temp/foo.sh - fails
> C:\temp> sh C:\temp\foo.sh - fails
> The failures were of a form where the first command on a line works but
> the second generates an error.
Sounds like the \r is being interpreted literally. Use POSIX paths, not
Windows paths, if you want your mount point settings to be honored.
> Oh, and when we downloaded just bash 3.1.6(17?) it didn't overwrite the
> old sh.
Get your versions right. That would be bash 3.1.17 release 6.
The bash postinstall script is designed for upgrades only. If /bin/sh is
newer in timestamp than the newly installed /bin/bash, no upgrade occurs.
This is a feature. However, it makes downgrades a little awkward. To
successfully downgrade, you need to manually 'cp /bin/bash.exe /bin/sh.exe'.
Life is short - so eat dessert first!
Eric Blake firstname.lastname@example.org
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v126.96.36.199 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin