From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest 28.0.90 is out
Date: Thu, 09 Dec 2021 19:00:12 +0800 [thread overview]
Message-ID: <878rwuavr7.fsf@yahoo.com> (raw)
In-Reply-To: <838rwuukkx.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Dec 2021 12:41:18 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: emacs-devel@gnu.org
>> Date: Thu, 09 Dec 2021 18:31:19 +0800
>>
>> > As for the rest, my recommendation is to implement futimens based on
>> > DJGPP's setftime.
>>
>> Thanks, but I'm confused with the DJGPP `struct ftime': do I have to
>> take leap years and the different lengths of each month into account
>> when setting the various members of a `struct ftime' from a time_t?
>
> No, you don't. You just populate these fields from the time value.
>
>> Alternatively, is there some function I overlooked that populates
>> `struct ftime' from time_t?
>
> Not directly, but you could use localtime to obtain a 'struct tm',
> then populate 'struct ftime' from that, with the necessary
> adjustments.
After implementing the missing functions, the linker complained about
duplicate copies of mktime, one in libc.a, and the other in gnulib's
mktime module, but I can't disable the mktime module, because the timegm
module doesn't work without mktime_internal, which is only defined in
mktime.c.
There is a mechanism for only building `mktime_internal' by only
defining `NEED_MKTIME_INTERNAL', but I don't know how to use it inside
gnulib.mk.
Or is some file supposed to include both timegm.c and mktime.c, or
something to that effect?
Thanks.
next prev parent reply other threads:[~2021-12-09 11:00 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 22:41 Emacs pretest 28.0.90 is out Stefan Kangas
2021-12-05 3:38 ` Po Lu
2021-12-05 8:00 ` Eli Zaretskii
2021-12-05 10:34 ` Po Lu
2021-12-05 10:59 ` Eli Zaretskii
2021-12-05 11:18 ` Po Lu
2021-12-05 11:24 ` Eli Zaretskii
2021-12-05 11:30 ` Po Lu
2021-12-05 13:48 ` Eli Zaretskii
2021-12-06 0:53 ` Po Lu
2021-12-06 12:49 ` Eli Zaretskii
2021-12-06 13:26 ` Po Lu
2021-12-06 13:41 ` Po Lu
2021-12-06 14:05 ` Eli Zaretskii
2021-12-07 0:42 ` Po Lu
2021-12-07 2:16 ` Po Lu
2021-12-07 13:40 ` Eli Zaretskii
2021-12-08 1:02 ` Po Lu
2021-12-08 12:37 ` Eli Zaretskii
2021-12-08 13:26 ` Po Lu
2021-12-08 13:36 ` Eli Zaretskii
2021-12-09 2:10 ` Po Lu
2021-12-09 9:16 ` Eli Zaretskii
2021-12-09 10:31 ` Po Lu
2021-12-09 10:41 ` Eli Zaretskii
2021-12-09 11:00 ` Po Lu [this message]
2021-12-09 12:16 ` Eli Zaretskii
2021-12-09 12:42 ` Po Lu
2021-12-09 12:43 ` Eli Zaretskii
2021-12-09 12:49 ` Po Lu
2021-12-09 12:56 ` Po Lu
2021-12-09 13:08 ` Eli Zaretskii
2021-12-09 13:18 ` Po Lu
2021-12-09 13:40 ` Eli Zaretskii
2021-12-09 13:42 ` Eli Zaretskii
2021-12-09 13:50 ` Po Lu
2021-12-09 13:47 ` Po Lu
2021-12-09 14:07 ` Eli Zaretskii
2021-12-09 14:24 ` Eli Zaretskii
2021-12-09 14:33 ` Eli Zaretskii
2021-12-09 14:44 ` Eli Zaretskii
2021-12-10 0:23 ` Po Lu
2021-12-10 0:44 ` Po Lu
2021-12-10 8:36 ` Eli Zaretskii
2021-12-10 9:35 ` Po Lu
2021-12-10 13:44 ` Po Lu via Emacs development discussions.
2021-12-10 14:26 ` Eli Zaretskii
2021-12-11 1:06 ` Po Lu
2021-12-11 8:08 ` Eli Zaretskii
2021-12-11 9:42 ` Po Lu via Emacs development discussions.
2021-12-11 11:23 ` Eli Zaretskii
2021-12-11 11:51 ` Po Lu
2021-12-06 13:55 ` Eli Zaretskii
2021-12-05 3:42 ` David O'Toole
2021-12-05 9:34 ` H. Dieter Wilhelm
2021-12-09 1:31 ` pretest installed (was: Emacs pretest 28.0.90 is out) andrés ramírez
2021-12-12 9:20 ` MingGW: Bug in TeX input-method?, was: Re: Emacs pretest 28.0.90 is out H. Dieter Wilhelm
2021-12-12 9:32 ` Eli Zaretskii
2021-12-12 15:48 ` H. Dieter Wilhelm
2021-12-12 16:03 ` Eli Zaretskii
2021-12-12 17:25 ` H. Dieter Wilhelm
2021-12-12 18:22 ` Eli Zaretskii
2021-12-12 19:20 ` Stefan Monnier
2021-12-12 21:44 ` TeX input method lacking subscript characters, was: Re: MingGW: Bug in TeX input-method? H. Dieter Wilhelm
2021-12-12 23:00 ` Stephen Berman
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=878rwuavr7.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--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 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.