Re: RFC: Adding a check to the top level configure script for a binary-mounted cygwin-hosted build directory

Eric Blake
2007-05-25T12:15:26Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Corinna Vinschen on 5/25/2007 3:47 AM:
>> IMHO the bug is that cygwin's bash isn't dealing with `` line endings
>> properly. It's the responsibility of the shell to strip trailing line
>> endings (1003.2-1992 3.6.3, although it doesn't mention
>> platform-specific line endings) during command substitution.
>>
>> Also, cygwin's bash should allow CR/LF pairs as word delimiters during
>> splitting, if it doesn't already. Cygwin supports mixed mounts, it
>> needs to deal with the ramifications itself.
>
> Does that actually happen with the latest bash? It should work fine
> on textmode mounts.

Currently, the only way to get cygwin to ignore \r inside `` pairs
(regardless of text or binary mount, since the text from `` is not coming
from the file system, but from a pipe) is to use the cygwin-specific igncr
shopt, or to add \r to IFS if the expansion of `` is subject to field
splitting. This is because with a cygwin-hosted build directory, the
default platform line ending is \n, not \r\n, for compatibility with
Linux. But ignoring \r is pretty easy; perhaps all that is needed is a
prep step in the cygwin-hosted build that does '(set -o igncr) 2>/dev/null
&& set -o igncr' before calling any djgpp processes inside ``.

- --
Don't work too hard, make some time for fun as well!

Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGVtNQ84KuGfSFAYARAiNUAJ91Pv9FvTfaNUxcDTXzXWnkQSj2DgCgm4+F
bKkCHboaSO9zkuQt7/s2Syg=
=wpI5
-----END PGP SIGNATURE-----