GNU bug report logs - #58224
29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file"

Previous Next

Full log

Message #44 received at 58224 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: acm <at> muc.de, stefankangas <at> gmail.com, 58224 <at> debbugs.gnu.org
Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el
 newer than byte-compiled file"
Date: Sun, 02 Oct 2022 20:07:26 +0300

> Date: Sun, 2 Oct 2022 16:46:01 +0000
> Cc: stefankangas <at> gmail.com, 58224 <at> debbugs.gnu.org, acm <at> muc.de
> From: Alan Mackenzie <acm <at> muc.de>
> 
> > > In lread.c I've got:
> 
> > >   struct timespec epoch_timespec = {(time_t)0, 0}; /* 1970-01-01T00:00 UTC */ 
> 
> > > , which clearly isn't satisfactory.
> 
> > I'm not sure I follow: why not satisfactory?
> 
> Don't we build for operating systems with different epochs?

No, the Epoch is the same for everyone.  It's a Posix notion, AFAIK.

> > Is mktime the function you are after?
> 
> Yes thanks!  But it's horribly complicated, involving wierd readings and
> settings of the TZ environment variable, and so on.

Not if you are interested in UTC.

> If a binary zero time would do (as above), maybe it would be
> satisfactory.  ;-)

Yes.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.