From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org
Subject: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file"
Date: Sun, 2 Oct 2022 16:46:01 +0000 [thread overview]
Message-ID: <YznAScQB9vyJ132p@ACM> (raw)
In-Reply-To: <83k05i1asd.fsf@gnu.org>
Hello, Eli.
On Sun, Oct 02, 2022 at 18:54:10 +0300, Eli Zaretskii wrote:
> > Date: Sun, 2 Oct 2022 15:38:25 +0000
> > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org
> > From: Alan Mackenzie <acm@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?
> > Can you (or anybody else) give me a clue as how to convert a human
> > readable time into a struct timespec? I've spent most of the
> > afternoon searching and grepping lots of .h files, and haven't come
> > up with anything, yet.
> 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. If a binary zero
time would do (as above), maybe it would be satisfactory. ;-)
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-10-02 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 14:15 bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Stefan Kangas
2022-10-01 14:29 ` Lars Ingebrigtsen
2022-10-01 14:50 ` Eli Zaretskii
2022-10-01 16:10 ` Stefan Kangas
2022-10-01 18:11 ` Alan Mackenzie
2022-10-01 21:15 ` Alan Mackenzie
2022-10-02 5:59 ` Eli Zaretskii
2022-10-02 10:43 ` Alan Mackenzie
2022-10-02 11:04 ` Eli Zaretskii
2022-10-02 11:32 ` Alan Mackenzie
2022-10-02 15:38 ` Alan Mackenzie
2022-10-02 15:54 ` Eli Zaretskii
2022-10-02 16:46 ` Alan Mackenzie [this message]
2022-10-02 17:07 ` Eli Zaretskii
2022-10-02 20:37 ` Alan Mackenzie
2022-10-02 21:29 ` Stefan Kangas
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=YznAScQB9vyJ132p@ACM \
--to=acm@muc.de \
--cc=58224@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefankangas@gmail.com \
/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).