X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_33,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
Message-ID:	<49F98B26.2070007@cornell.edu>
Date:	Thu, 30 Apr 2009 07:27:34 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Bash problem
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

A build script I was running failed because it had a command of the form 
'eval foo=bar time <command>'.  Here's a simple test case:

$ eval foo=bar time true
-bash: time: command not found

It works fine without foo=bar:

$ eval time true

real    0m0.060s
user    0m0.000s
sys     0m0.000s

I have access to a linux system in which the original command (with 
foo=bar) works.  That system has an older version of bash.  Is this a 
bug in the current bash?  Or the cygwin build of bash?

Ken


--
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/

- Raw text -