Sebastian Freundt

Oh, and in case you're building the tarball it's much easier: Delete the GNUmakefile and kick `build-aux` from `SUBDIRS` in the main Makefile.

Oh yes, that rings a bell. That is the test to determine the zone file layout. That test (and possibly others) isn't cross-compile-proof. I suppose you could set the variable...

Try dd9c6675b for a configure run without deep inspection of zoneinfo files.

Thanks for reporting the `ltrcc` issue. Yes it seems tough. Without getting a second configure script involved that configures for --build==--host I don't see either how to get this built...

Hi, thanks for the report. Let me point out that 14:14 is read as 14:14:00, and similarly 16:47 is read as 16:47:00, i.e. seconds have been omitted in both cases.

Hey Matt, good catch! Fix is in a669bba8d.

Hey, thanks for the question. Unfortunately the answer is that this is out of dateutils' scope. By my design choice everything has to be explicit, there's no magic background variables...

Well, yes, that's what I warned about. Dateutils are portable in the sense that they produce the same result on any machine regardless of underlying operating system or local settings,...

@archenemies No, I'm not against environment variables, I'm against implicit magic. Explicitly stating the zone in the command-line beats using context derived somehow from the system or the environment, in...

Yes sorry you're right. POSIX leaves that case unspecified, both for `date(1)` and `tzname(3)`, only guarantees `tzset()` shall succeed, not mentioning gmtime, localtime, etc. > If your users find themselves...