Re: Epoch in 1.7.34

2015-05-27 Thread Warren Young
On May 27, 2015, at 10:25 AM, Andrew Clark wrote: > > strace.exe: error creating process date, (error 2) Well, there’s your problem. You will find that “which date” either doesn’t give “/usr/bin/date” as a result, or that the executable there is broken somehow. In either case, you need to re

Re: Epoch in 1.7.34

2015-05-27 Thread Andrew Clark
On May 20, 2015, at 2:11 PM, Warren Young wrote: > > So, what's the TZ setting on the 1.7.34 box? $ echo $TZ $ Let me try exporting TZ and running it again. BTW, in answer to your previous question, strace returns $ strace -fq date +%s strace.exe: error creating process date, (error 2) $ echo

Re: Epoch in 1.7.34

2015-05-20 Thread Warren Young
On May 20, 2015, at 1:50 PM, Warren Young wrote: > > More likely, the change is in newlib or the terminal I/O code. Or, it could be in /bin/date itself, part of coreutils. I see this in the latest version’s NEWS file: date could crash or go into an infinite loop when parsing a malformed TZ=

Re: Epoch in 1.7.34

2015-05-20 Thread Warren Young
On May 20, 2015, at 11:33 AM, Andrew Clark wrote: > > I'm not sure if this a Cygwin question or a bash question, but I came > here first. Given that date is not a Bash builtin, I don’t know why that’s even on the table. The Cygwin DLL *is* involved, but a problem in the key function (time(2))

Epoch in 1.7.34

2015-05-20 Thread Andrew Clark
Hi, I was wondering about this behavior of the date command in Cygwin 1.7.34. The bash version is 4.1.17: $ date +%s $ The behavior has been corrected in 2.0.2 (bash version 4.3.33): $ date +%s 1432142822 $ I'm not sure if this a Cygwin question or a bash question, but I came here first. Than