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/
