Bash problem

[david sastre]

2009/4/30 Ken Brown <kbrown@cornell.edu>:
> 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/
>
>

Hi there. I'm using

$ uname -a
CYGWIN_NT-5.1 sith 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin

and

$ cygcheck -c time bash
Cygwin Package Information
Package              Version        Status
bash                 3.2.48-21      OK
time                  1.7-2          OK


testing your example gives me

$ eval foo=bar time true
0.03user 0.03system 0:00.06elapsed 91%CPU (0avgtext+0avgdata 205568maxresident)k
0inputs+0outputs (811major+0minor)pagefaults 0swaps



Maybe your using

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