From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#33847: 27.0.50; emacsclient does not find server socket Date: Sun, 25 Jul 2021 09:32:32 +0300 Message-ID: <83a6maykcf.fsf@gnu.org> References: <8a6fc59c-08b3-e274-4fb1-74674c79540a@cs.ucla.edu> <27d2f2eb-8956-4088-f3ec-5ff6c2cf2e8f@cs.ucla.edu> <87eeo27v6k.fsf@gnus.org> <83lfi79klf.fsf@gnu.org> <831rjya5yy.fsf@gnu.org> <8333533f-08ec-acd4-2fbf-f06e78591e98@cs.ucla.edu> <83v9h99awv.fsf@gnu.org> <878s1yjy20.fsf@gnus.org> <83lf5y2t78.fsf@gnu.org> <878s1yi8jc.fsf@gnus.org> <83h7gm2r4j.fsf@gnu.org> <87wnphe06g.fsf@gnus.org> <87r1fpdzuy.fsf@gnus.org> <838s1w1b7x.fsf@gnu.org> <5f457b50-c1bd-4856-33c7-f85edf111bd0@cs.ucla.edu> <83v950yv7i.fsf@gnu.org> <5d2f6394-2fc0-e20a-9018-0ea59f399ba2@cs.ucla.edu> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38320"; mail-complaints-to="usenet@ciao.gmane.io" Cc: teika@gmx.com, 33847@debbugs.gnu.org, larsi@gnus.org, ulm@gentoo.org To: Paul Eggert Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jul 25 08:33:11 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m7XhG-0009kP-3e for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 25 Jul 2021 08:33:10 +0200 Original-Received: from localhost ([::1]:47208 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7XhE-0003qM-Vk for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 25 Jul 2021 02:33:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43658) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7Xh7-0003po-TB for bug-gnu-emacs@gnu.org; Sun, 25 Jul 2021 02:33:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:35849) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m7Xh7-0004Yu-LK for bug-gnu-emacs@gnu.org; Sun, 25 Jul 2021 02:33:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1m7Xh7-00083u-Ji for bug-gnu-emacs@gnu.org; Sun, 25 Jul 2021 02:33:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 25 Jul 2021 06:33:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33847 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 33847-submit@debbugs.gnu.org id=B33847.162719477430975 (code B ref 33847); Sun, 25 Jul 2021 06:33:01 +0000 Original-Received: (at 33847) by debbugs.gnu.org; 25 Jul 2021 06:32:54 +0000 Original-Received: from localhost ([127.0.0.1]:47394 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m7Xgz-00083W-KN for submit@debbugs.gnu.org; Sun, 25 Jul 2021 02:32:54 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:45884) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m7Xgx-00083J-SW for 33847@debbugs.gnu.org; Sun, 25 Jul 2021 02:32:53 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60228) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7Xgr-0004MN-RO; Sun, 25 Jul 2021 02:32:45 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4238 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7Xgr-0005mw-F9; Sun, 25 Jul 2021 02:32:45 -0400 In-Reply-To: <5d2f6394-2fc0-e20a-9018-0ea59f399ba2@cs.ucla.edu> (message from Paul Eggert on Sat, 24 Jul 2021 16:31:21 -0700) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:210681 Archived-At: > Cc: larsi@gnus.org, teika@gmx.com, 33847@debbugs.gnu.org, ulm@gentoo.org > From: Paul Eggert > 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.