From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: teika@gmx.com, 33847@debbugs.gnu.org, larsi@gnus.org, ulm@gentoo.org
Subject: bug#33847: 27.0.50; emacsclient does not find server socket
Date: Sun, 25 Jul 2021 09:32:32 +0300 [thread overview]
Message-ID: <83a6maykcf.fsf@gnu.org> (raw)
In-Reply-To: <5d2f6394-2fc0-e20a-9018-0ea59f399ba2@cs.ucla.edu> (message from Paul Eggert on Sat, 24 Jul 2021 16:31:21 -0700)
> Cc: larsi@gnus.org, teika@gmx.com, 33847@debbugs.gnu.org, ulm@gentoo.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 24 Jul 2021 16:31:21 -0700
>
> In looking into this, I noticed that our current approach has another
> problem, because admin/merge-gnulib avoids Gnulib's malloc-posix module
> so that the Emacs build procedure need not worry about Gnulib's malloc
> interposition on MS-Windows. However, Gnulib relies on the POSIX malloc
> spec in its own use of malloc, so malloc-posix should be present in
> Emacs; this is for the benefit of some platforms that are neither GNU
> nor MS-Windows.
>
> What we should do is (A) have the Emacs tarball contain whatever Gnulib
> memory-allocation modules Gnulib needs, (B) arrange for Gnulib's
> memory-allocation modules to be inactive on MS-Windows, and (C) arrange
> for Emacs's private implementation of malloc/realloc/free to be
> GNU-compatible.
Right.
> Proposed patches attached to do all this. Patch 4/4 is the one needing
> most scrutiny, since it involves MS-Windows which I don't use.
Thanks, will review that shortly.
> > Can you tell which Gnulib modules are affected by the new
> > "--disable-year2038" option?
>
> No modules are affected by the --disable-year2038 option on MS-Windows.
>
> The --disable-year2038 option has an effect only on 32-bit GNU/Linux x86
> and ARM (glibc 2.34 and later). On these platforms, the option affects a
> good many Gnulib modules as well as Emacs source code directly. This is
> because the option affects anything that gets or sets a timestamp from
> the OS. 'stat' syscalls, for example.
>
> As I understand it, MS-Windows switched to 64-bit time_t back in 2005
> (even on 32-bit platforms), and nowadays you have to explicitly request
> 32-bit time_t (does anybody do that when building Emacs? I hope not).
This is only mostly correct. It is true that MS-Windows switched to
64-bit time_t as the preferred method some time ago even on 32-bit
versions of Windows. But to build an Emacs that will run on versions
of Windows before the switch, which means all versions before XP, you
_must_ compile with 32-bit time_t, because those older platforms
simply don't have the 64-bit time_t variants of relevant libc
functions in their C runtime DLL, so Emacs using 64-bit time_t will
refuse to start on them. And since we still try to support those
older systems, the 32-bit build of Emacs on Windows does use 32-bit
time_t -- if it is built with mingw.org's MinGW (where time_t is a
32-bit type by default, so no need for any specific requests), because
MinGW64 tossed the support for those older versions long ago, and thus
even its 32-bit versions cannot be used to build an Emacs which will
run on anything before Vista.
> The --disable-year2038 option does not have any effect on MS-Windows,
> because nobody has bothered to add support for that option on that
> platform and I expect and hope that nobody ever will.
So therefore my question seems to be even more important than I
thought, and I'm still asking which Gnulib modules are affected by
this, because I'd need to audit them carefully to see whether the
32-bit MS-Windows build with mingw.org's MinGW could be affected. Can
you show the list of those modules (out of those which Emacs imports),
so I could take a look at them?
> Any Emacs executables built with the --disable-year2038 option on
> GNU/Linux x86 or ARM will of course stop working after 2038, so it's not
> an option I recommend.
That's 17 years in the future, so it will be a real concern in about
15 years, I'd say. let's talk then ;-)
Thanks.
next prev parent reply other threads:[~2021-07-25 6:32 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 9:48 bug#33847: 27.0.50; emacsclient does not find server socket Ulrich Mueller
2018-12-23 16:20 ` Ulrich Mueller
2018-12-25 21:02 ` Paul Eggert
2018-12-25 23:29 ` Ulrich Mueller
2018-12-26 0:24 ` Paul Eggert
2018-12-26 2:27 ` Ulrich Mueller
2018-12-26 6:59 ` Paul Eggert
2018-12-26 15:14 ` Ulrich Mueller
2018-12-26 18:32 ` Paul Eggert
2018-12-28 6:37 ` Ulrich Mueller
2018-12-30 6:47 ` Paul Eggert
2018-12-27 3:38 ` Richard Stallman
2018-12-27 16:42 ` Paul Eggert
2018-12-27 17:13 ` Paul Eggert
2018-12-28 6:19 ` Ulrich Mueller
2018-12-28 6:35 ` Paul Eggert
2018-12-28 6:51 ` Ulrich Mueller
2018-12-30 6:44 ` Paul Eggert
2019-01-20 17:59 ` Ulrich Mueller
2019-02-10 8:37 ` Ulrich Mueller
2019-02-10 9:48 ` Eli Zaretskii
2020-08-19 11:05 ` Lars Ingebrigtsen
2020-08-21 21:28 ` Paul Eggert
2020-08-22 7:24 ` Ulrich Mueller
2020-08-22 7:33 ` Andreas Schwab
2020-08-22 7:45 ` Ulrich Mueller
2020-08-22 8:00 ` Eli Zaretskii
2020-08-22 17:51 ` Paul Eggert
2020-08-22 7:59 ` Eli Zaretskii
2020-08-22 17:55 ` Paul Eggert
2020-08-22 18:30 ` Eli Zaretskii
2020-08-22 21:20 ` Paul Eggert
2020-08-23 5:41 ` Eli Zaretskii
2021-07-22 13:08 ` Lars Ingebrigtsen
2021-07-22 16:45 ` Eli Zaretskii
2021-07-22 17:05 ` Lars Ingebrigtsen
2021-07-22 17:30 ` Eli Zaretskii
2021-07-23 11:31 ` Lars Ingebrigtsen
2021-07-23 11:38 ` Lars Ingebrigtsen
2021-07-23 23:58 ` Paul Eggert
2021-07-24 6:23 ` Eli Zaretskii
2021-07-24 7:48 ` Paul Eggert
2021-07-24 8:25 ` Eli Zaretskii
2021-07-24 23:31 ` Paul Eggert
2021-07-25 6:32 ` Eli Zaretskii [this message]
2021-07-25 16:22 ` Paul Eggert
[not found] ` <a0688fd6-9e73-73d8-6138-3280981abcb5@cs.ucla.edu>
2021-07-25 16:34 ` Eli Zaretskii
2021-10-04 6:45 ` Paul Eggert
2021-07-25 7:27 ` Eli Zaretskii
2021-07-24 10:11 ` Lars Ingebrigtsen
2021-07-24 19:37 ` Paul Eggert
2021-07-23 11:58 ` Eli Zaretskii
2021-07-22 18:30 ` Ulrich Mueller
2019-04-27 1:41 ` Teika Kazura
2019-04-27 7:56 ` Eli Zaretskii
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=83a6maykcf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33847@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=teika@gmx.com \
--cc=ulm@gentoo.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).