From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19088 invoked by alias); 25 May 2007 12:15:26 -0000 Received: (qmail 19053 invoked by uid 22791); 25 May 2007 12:15:11 -0000 X-Spam-Check-By: sourceware.org Received: from alnrmhc16.comcast.net (HELO alnrmhc16.comcast.net) (206.18.177.56) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 May 2007 12:15:09 +0000 Received: from [192.168.0.103] (c-71-199-58-92.hsd1.ut.comcast.net[71.199.58.92]) by comcast.net (alnrmhc16) with ESMTP id <20070525121506b1600gc9i6e>; Fri, 25 May 2007 12:15:07 +0000 Message-ID: <4656D351.9010702@byu.net> Date: Fri, 25 May 2007 12:15:00 -0000 From: Eric Blake User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: binutils@sourceware.org, gdb-patches@sourceware.org, nickc@redhat.com, bonzini@gnu.org, aoliva@redhat.com, DJ Delorie Subject: Re: RFC: Adding a check to the top level configure script for a binary-mounted cygwin-hosted build directory References: <46543BE2.1010209@lu.unisi.ch> <46555F35.40003@redhat.com> <200705241426.l4OEQ0gA020722@greed.delorie.com> <4655AEA3.7080309@redhat.com> <200705241542.l4OFgi0v023645@greed.delorie.com> <20070525094707.GA16127@calimero.vinschen.de> In-Reply-To: <20070525094707.GA16127@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-05/txt/msg00388.txt.bz2 -----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-----