X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Michael Hoffman Subject: Re: \r in variables and test Date: Mon, 23 Apr 2007 01:08:24 +0100 Lines: 25 Message-ID: References: <20070422170609.GV7781@interface.famille.thibault.fr> <20070422174834.GY7781@interface.famille.thibault.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) In-Reply-To: <20070422174834.GY7781@interface.famille.thibault.fr> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com [Samuel Thibault] >>> In a ./configure script, I call a test program (native python, actually) >>> that outputs "True\r\n" and I put this result in variable foo. The >>> problem is that [ "$foo" = True ] doesn't return true because foo >>> actually contains True\r, not True. [Michael Hoffman] >> * [ ${foo/%$'\r'/} = True ] [Samuel Thibault] > This looks saner, but shouldn't the test program always do this itself? Well it's not test (or even the test built-in in bash) that strips out \n, but bash when you originally represent the output of the command in a variable. I don't know whether it would be a good idea for it to strip \r as well. > Anyhow, the place that needs to be fixed is rather > /us/share/autoconf-archive/ac_python_devel.m4 I think what needs to be fixed is the expectation that you can mix non-Cygwin Python with Cygwin everything else and things will work seamlessly. ;) -- Michael -- 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/