From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: windows build failure
Date: Sat, 12 Oct 2013 23:03:00 +0300 [thread overview]
Message-ID: <838uxyqmtn.fsf@gnu.org> (raw)
In-Reply-To: <52599F44.9030609@cs.ucla.edu>
> Date: Sat, 12 Oct 2013 12:13:08 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: emacs-devel@gnu.org
>
> >> > if you set your
> >> > system clock to 1116918-05-14 19:20:32 UTC on such a host,
> >> > or otherwise deal with outlandish time stamps, Emacs will
> >> > have screwups, and it won't be trivial to fix this.
>
> > So you are saying that 32-bit hosts will be dead for Emacs in about
> > half a year (if I interpret that time stamp correctly), is that right?
>
> No, it's A.D. 1,116,918, i.e., more than a million years
> from now.
That's a relief.
> Pretty outlandish, admittedly, but people often
> use Emacs for outlandish things. On my 64-bit host with
> TZ=UTC0, (current-time-string '(536870912 0)) returns
> "Sat May 14 19:20:32 1116918", the correct value;
> on GNU/Linux x32, though, Emacs configured without --with-wide-int
> will report an error even though that platform's 64-bit time_t
> can represent that time stamp; this is because 536870912 doesn't
> fit in an Emacs integer when EMACS_INT is 32 bits.
I get "Invalid time specification" with 536870912 on Windows. But I
also get that error for any value beyond 32767 (that corresponds to
"Mon Jan 18 11:01:52 2038"), as I'd expect for a 32-bit time_t. Am I
missing something?
next prev parent reply other threads:[~2013-10-12 20:03 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 21:45 windows build failure Sean Sieger
2013-09-18 6:42 ` Eli Zaretskii
2013-09-18 6:56 ` Dani Moncayo
2013-09-18 7:23 ` Eli Zaretskii
2013-09-18 12:37 ` Sean Sieger
2013-09-18 12:44 ` Eli Zaretskii
[not found] ` <CADWZ7fL5iWhAWqrc8RqipO3Zgaz=AygHPUhhTNG97zTVaxpE3g@mail.gmail.com>
2013-09-18 12:46 ` Eli Zaretskii
2013-09-18 13:08 ` Sean Sieger
2013-09-18 13:18 ` Eli Zaretskii
2013-09-18 13:25 ` Sean Sieger
2013-09-18 14:48 ` Eli Zaretskii
2013-09-18 15:15 ` Sean Sieger
2013-09-18 15:28 ` Eli Zaretskii
2013-09-18 15:38 ` Sean Sieger
2013-09-19 14:14 ` Sean Sieger
2013-09-19 14:24 ` Eli Zaretskii
2013-09-19 17:33 ` Sean Sieger
2013-09-19 18:46 ` Eli Zaretskii
2013-09-19 20:25 ` Sean Sieger
2013-09-20 7:28 ` Eli Zaretskii
2013-09-20 14:24 ` Sean Sieger
2013-09-20 15:16 ` Eli Zaretskii
2013-09-20 16:23 ` Sean Sieger
2013-09-20 16:34 ` Sean Sieger
2013-09-20 17:40 ` Eli Zaretskii
2013-10-12 13:31 ` Eli Zaretskii
2013-10-12 15:55 ` Paul Eggert
2013-10-12 16:49 ` Eli Zaretskii
2013-10-12 19:13 ` Paul Eggert
2013-10-12 20:03 ` Eli Zaretskii [this message]
2013-10-12 21:45 ` Paul Eggert
2013-10-12 19:31 ` Sean Sieger
2013-10-14 12:41 ` Sean Sieger
2013-10-14 16:25 ` Eli Zaretskii
2013-10-14 17:31 ` Sean Sieger
2013-10-14 18:02 ` Sean Sieger
2013-10-14 18:10 ` Eli Zaretskii
2013-10-14 19:06 ` Sean Sieger
2013-10-14 19:13 ` Eli Zaretskii
2013-10-14 19:24 ` Sean Sieger
-- strict thread matches above, loose matches on Subject: below --
2013-05-26 20:29 Sean Sieger
2013-05-27 16:36 ` Eli Zaretskii
2013-05-27 18:07 ` Óscar Fuentes
2013-05-27 19:10 ` Eli Zaretskii
2013-05-27 19:56 ` Óscar Fuentes
2013-05-28 18:19 ` Sean Sieger
2013-05-28 19:07 ` Eli Zaretskii
2013-05-29 13:15 ` rzl24ozi
2013-05-29 15:21 ` Eli Zaretskii
2013-05-29 15:50 ` Óscar Fuentes
2013-05-29 17:17 ` Eli Zaretskii
2013-05-29 17:02 ` Paul Eggert
2013-05-29 17:20 ` Eli Zaretskii
2013-05-29 18:55 ` Paul Eggert
2013-05-29 20:28 ` Eli Zaretskii
2013-05-29 21:27 ` Paul Eggert
2013-05-30 2:46 ` Eli Zaretskii
2013-05-29 23:35 ` rzl24ozi
2013-05-30 18:03 ` Eli Zaretskii
2013-05-30 19:38 ` rzl24ozi
2013-05-31 8:50 ` Eli Zaretskii
2013-05-29 16:06 ` cg
2013-05-29 17:21 ` Eli Zaretskii
2012-07-29 16:40 Windows " Dani Moncayo
2012-07-29 16:49 ` Dani Moncayo
2011-02-21 19:37 windows " Sean Sieger
2011-02-21 19:40 ` Sean Sieger
2011-02-21 19:46 ` Christoph
2011-02-21 19:48 ` Paul Eggert
2011-02-21 20:21 ` Eli Zaretskii
2011-02-21 20:29 ` Lennart Borgman
2011-02-21 22:50 ` Sean Sieger
2011-02-21 20:37 ` Eli Zaretskii
2011-02-22 2:09 ` Paul Eggert
2011-02-22 8:57 ` Eli Zaretskii
2011-02-22 9:40 ` Paul Eggert
2011-02-22 10:49 ` Eli Zaretskii
2011-02-22 21:44 ` Paul Eggert
2011-02-23 9:47 ` Eli Zaretskii
2011-02-23 10:32 ` Eli Zaretskii
2011-02-25 21:28 ` Paul Eggert
2011-02-14 16:47 Sean Sieger
2011-02-14 16:54 ` Tom Tromey
2011-02-14 17:17 ` Eli Zaretskii
2011-02-14 17:20 ` Sean Sieger
2011-02-14 17:49 ` Eli Zaretskii
2011-02-14 18:02 ` Tom Tromey
2011-02-14 20:43 ` Sean Sieger
2011-01-03 17:57 Sean Sieger
2011-01-03 19:37 ` Eli Zaretskii
2010-08-02 15:01 Sean Sieger
2010-08-02 15:05 ` Juanma Barranquero
2010-08-02 15:16 ` Sean Sieger
2010-07-19 14:42 Sean Sieger
2010-07-19 15:03 ` Óscar Fuentes
2010-07-19 15:30 ` Juanma Barranquero
2010-07-19 17:45 ` Eli Zaretskii
2010-07-20 18:33 ` Juanma Barranquero
2010-07-19 18:35 ` Sean Sieger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838uxyqmtn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).