From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 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, 02 Oct 2022 18:54:10 +0300 [thread overview]
Message-ID: <83k05i1asd.fsf@gnu.org> (raw)
In-Reply-To: <YzmwcTF00juPQ1mr@ACM> (message from Alan Mackenzie on Sun, 2 Oct 2022 15:38:25 +0000)
> 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?
> 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?
next prev parent reply other threads:[~2022-10-02 15:54 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 [this message]
2022-10-02 16:46 ` Alan Mackenzie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k05i1asd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58224@debbugs.gnu.org \
--cc=acm@muc.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.