[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug#33847: 27.0.50; emacsclient does not find server socket
From: |
Eli Zaretskii |
Subject: |
Re: bug#33847: 27.0.50; emacsclient does not find server socket |
Date: |
Sun, 25 Jul 2021 19:34:47 +0300 |
> Cc: larsi@gnus.org, teika@gmx.com, 33847@debbugs.gnu.org, ulm@gentoo.org,
> Gnulib bugs <bug-gnulib@gnu.org>
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 25 Jul 2021 09:22:06 -0700
>
> On 7/24/21 11:32 PM, Eli Zaretskii wrote:
>
> >> No modules are affected by the --disable-year2038 option on MS-Windows.
>
> It turns out that I was wrong about that. (I don't normally look at the
> MS-Windows part of Gnulib and misunderstood some of the code I was
> reading.) Please see gnulib/m4/year2038.m4 for details. This file is in
> the patches I sent, or you can see it directly here:
>
> https://git.savannah.gnu.org/cgit/gnulib.git/tree/m4/year2038.m4
>
> This code knows about MS-Windows, Mingw, _USE_32BIT_TIME_T,
> __MINGW_USE_VC2005_COMPAT, and so forth, and attempts to do the right
> thing. As near as I can make out it should work for the scenario you
> describe, but I don't use MS-Windows so I could well be wrong. If I'm
> wrong and this code doesn't do what you want, I suggest contacting
> bug-gnulib to alert Bruno Haible, who wrote that part of the code. I'll
> cc bug-gnulib so that Bruno sees this email. (Bruno, this discussion is
> at <https://bugs.gnu.org/33847#161>.)
Thanks, I will take a look, although I now understand it isn't urgent,
since Emacs doesn't (yet) use the year2038 module.
> > 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.
>
> There should be no need to audit, because Gnulib still supports
> platforms that have only 32-bit time_t.
>
> Gnulib is agnostic about time_t width, and is supposed to work even if
> time_t is 40 bits (which it is on a very few mainframes) or any other
> width. We regularly test it only on 32- and 64-bit time_t, though.
Thanks, that's good to know.