From debbugs-submit-bounces@debbugs.gnu.org Sat Oct 01 10:15:34 2022 Received: (at submit) by debbugs.gnu.org; 1 Oct 2022 14:15:34 +0000 Received: from localhost ([127.0.0.1]:45472 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oedHC-0008SS-1I for submit@debbugs.gnu.org; Sat, 01 Oct 2022 10:15:34 -0400 Received: from lists.gnu.org ([209.51.188.17]:47682) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oedH9-0008M0-MU for submit@debbugs.gnu.org; Sat, 01 Oct 2022 10:15:33 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40212) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oedH6-0001BY-2l for bug-gnu-emacs@gnu.org; Sat, 01 Oct 2022 10:15:31 -0400 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]:33544) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oedH0-0004um-Cy for bug-gnu-emacs@gnu.org; Sat, 01 Oct 2022 10:15:25 -0400 Received: by mail-oi1-x22c.google.com with SMTP id j188so7514520oih.0 for ; Sat, 01 Oct 2022 07:15:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:from:to:cc:subject:date; bh=OZR3DzwiUR7R9qldp+HFPCEHot5sOhU9EdXwDxlPexY=; b=R407ubGu03IYkm9Vke+6HRgq7yRXlT9nz5kZUx7k31qQuASbZJ96ayIvLi0Tve25VU wJGJ1Xs14/hWLJpCRRKt7UHscN8rlVBEri4a7sHjsoBtgfT2Xn5BwH568lNrpCJEaZ2h nvhoXfd0Ma20Y3DzkmVjhYz3WslpIq3Irw2l/OTnBj6Epe8ecNlZOu/NK93vSiRKwz4V 6UEHXgSm6X7hq71kxeKiZUiSmuSPFCBHBv8ompZmZqHDkZyLaGtzJwbxFkgq55cP9ai/ mrrkdfwE0dGIL7kXcYMCW2idvQWmIEppZ71WDcOz1D34hY9Um/UN0/hOwoexBMdpszVo vB8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:to:subject:message-id:date:from :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=OZR3DzwiUR7R9qldp+HFPCEHot5sOhU9EdXwDxlPexY=; b=kf2aZB/p3x2GxtdpANxSnR+tLvehEs4fKne8RGEX/5nlilMIW2hLnlAoo/3LYKvRkG gfAPkHPpFDtlAaW7r76AY4VlQpacBhZe7xGKIeT2jcHznlQtRDoDzIXdrnLNeAHMAcST yP84hcqgqO6utmju7v4QRVZjgLX7+A50DBiULhcyrfcaKazOGczqx3SvEXsoQ1arCtIf 3U+TPPyuJzxMQ7fKUy124OnrZhnJ67gPq/T0nCbXQ+rec19LhyUCBJ2I/78DsXnWN9EB qsTnlItQ1odFYn7Xm8CRTo2RleHqjFmjB1ELx02Aul4GAaRveEeWfGZ+U5JUsaHgcw7o Boeg== X-Gm-Message-State: ACrzQf1L7Mdb82TFH72cFBWE3QJl6TA+KkgNFUWbZggOO0X77LTF3AOE gTJEsiY8/MTFNQ54hSb7bOz8i235qyITc+kIkNw0efOo6A0= X-Google-Smtp-Source: AMsMyM6RNEwcYPaTtj57zsZuX3M/cqebU1ImPRSx9CthFT2+0xDU86slPE5aO6OtNfah/6aKqvLPn6jQkjzEDlp38Xw= X-Received: by 2002:a05:6808:1688:b0:345:ea9a:2954 with SMTP id bb8-20020a056808168800b00345ea9a2954mr1188962oib.199.1664633720790; Sat, 01 Oct 2022 07:15:20 -0700 (PDT) MIME-Version: 1.0 From: Stefan Kangas Date: Sat, 1 Oct 2022 16:15:09 +0200 Message-ID: Subject: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" To: bug-gnu-emacs@gnu.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::22c; envelope-from=stefankangas@gmail.com; helo=mail-oi1-x22c.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.3 (-) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) Severity: wishlist Every time I "make bootstrap", I get a ton of spurious messages (see below). I believe they started showing up with Lars' much appreciated work on improving build speeds. I have tripped myself up over this more than once, and I suspect it will confuse users too. Is there any chance we could do something to silence them? If we can't solve it "properly", how about just a hack? For example, could we add some variable to suppress these messages at this stage of the build process? For completeness, I almost always build --with-native-compilation, in case that matters. ELC+ELN emacs-lisp/cconv.elc ELC+ELN emacs-lisp/byte-opt.elc ELC+ELN emacs-lisp/bytecomp.elc ELC+ELN emacs-lisp/comp.elc ELC+ELN emacs-lisp/comp-cstr.elc Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp.el=E2=80= =99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/bytecomp.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp.el=E2=80= =99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/bytecomp.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/cconv.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/cconv.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp.el=E2=80= =99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp.el=E2=80= =99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp.el=E2=80= =99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/bytecomp.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/cconv.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/bytecomp.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/bytecomp.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/cconv.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/cconv.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/icons.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/icons.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/icons.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/icons.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp-cstr.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp-cstr.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp-cstr.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/icons.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp-cstr.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp-cstr.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/byte-opt.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/byte-opt.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/byte-opt.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/byte-opt.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/byte-opt.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/comint.el=E2=80=99 newer= than byte-compiled file; using older file ELC+ELN emacs-lisp/loaddefs-gen.elc Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp.el=E2=80= =99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/bytecomp.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/icons.el=E2= =80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/comp-cstr.el= =E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/Users/skangas/wip/emacs/lisp/emacs-lisp/byte-opt.el= =E2=80=99 newer than byte-compiled file; using older file From debbugs-submit-bounces@debbugs.gnu.org Sat Oct 01 10:29:50 2022 Received: (at 58224) by debbugs.gnu.org; 1 Oct 2022 14:29:50 +0000 Received: from localhost ([127.0.0.1]:45492 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oedV0-0000vm-3w for submit@debbugs.gnu.org; Sat, 01 Oct 2022 10:29:50 -0400 Received: from quimby.gnus.org ([95.216.78.240]:39674) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oedUy-0000vZ-73 for 58224@debbugs.gnu.org; Sat, 01 Oct 2022 10:29:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=m2gjCW+ruXi9N7Jae50z6cyGoGEajGWoGVl2ojQn3Sg=; b=lVuABT9rrhxtheadJ1p/qtRJT1 kp6d5QSTN1RjH1DBqdqHqxgnnQF8tjfRGUNH949S8y0e2GNse25j/ka9DCIgJrlRKqiKDS/T+5Pge RaRUwl8zWVjvYhSG8wBu3HTnEI+cUulJZKeBqqvCVp4nupm0Sy2DTA85B/4Nzzp/Yvaw=; Received: from [84.212.220.105] (helo=downe) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oedUo-0004vh-Bt; Sat, 01 Oct 2022 16:29:41 +0200 From: Lars Ingebrigtsen To: Stefan Kangas Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" In-Reply-To: (Stefan Kangas's message of "Sat, 1 Oct 2022 16:15:09 +0200") References: Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAgMAAAAqbBEUAAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAADFBMVEVCODWPWVXVz7// //8bs5b3AAAAAWJLR0QDEQxM8gAAAAd0SU1FB+YKAQ0qMyamE5YAAAGOSURBVCjPRdLBauMwEAbg XyY2rU5msaHJaQ89FD+FtCSh7MkNUg4+hdLC1k+hhhDYnNxSFzYnH5yA5yk7kklXhxEfM0KjsRGL vXA5gLh+4dhqxxF5/cFxIwKiY8ZxMkJUZdhc5KaYVhmotevX9/4Of6RHRVvqb+IXOQFB6T01maSD wtJ0eksOBR0ctFF6W9x7NPgVT/R+dqWSgbFE/rrHtH+kQ4ejyWkHMTTPvz2sbypykB0+OcPtRPNU NqCn5OwQz6Ty4OUgzIihJiegJKTChziRuwauIec4aVc0CABW3JYHl6WAEjQwkgAkdFL8XPDjqjKh M4RVkAbHNK4/lbAl5A5/kdT/AGsgHdpc/hi0yhm+nYrozDOyVQNrfXfUrok2YbDts9WMEnxFRMcG 1QWOQ+ERykSGmkiNHyNq/oOE8mWMmKFuJXmUKVake485YsUZ3XlMxjOqmzGyEe5nccGK3m/qAAOs 27dbn0nDRNvd05I3jJibxTf8cPiQ9agX1j4weh78wv8XFC4dFnRZ5gu0PLNQPKOFAwAAACV0RVh0 ZGF0ZTpjcmVhdGUAMjAyMi0xMC0wMVQxMzo0Mjo1MSswMDowMJO9LnIAAAAldEVYdGRhdGU6bW9k aWZ5ADIwMjItMTAtMDFUMTM6NDI6NTErMDA6MDDi4JbOAAAAAElFTkSuQmCC X-Now-Playing: The Heart Throbs's _Make More Noise (4)_: "Toy" Date: Sat, 01 Oct 2022 16:29:37 +0200 Message-ID: <87y1tzehwu.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Stefan Kangas writes: > Every time I "make bootstrap", I get a ton of spurious messages (see > below). I believe they started showing up with Lars' much appreciated > work on improving build speeds. Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58224 Cc: 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Stefan Kangas writes: > Every time I "make bootstrap", I get a ton of spurious messages (see > below). I believe they started showing up with Lars' much appreciated > work on improving build speeds. No, I think they were there before that. > Is there any chance we could do something to silence them? If we > can't solve it "properly", how about just a hack? For example, could > we add some variable to suppress these messages at this stage of the > build process? Yes, making the warnings go away would be nice. From debbugs-submit-bounces@debbugs.gnu.org Sat Oct 01 10:50:57 2022 Received: (at 58224) by debbugs.gnu.org; 1 Oct 2022 14:50:57 +0000 Received: from localhost ([127.0.0.1]:45524 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oedpR-0001VB-0k for submit@debbugs.gnu.org; Sat, 01 Oct 2022 10:50:57 -0400 Received: from eggs.gnu.org ([209.51.188.92]:52538) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oedpP-0001Uy-K0 for 58224@debbugs.gnu.org; Sat, 01 Oct 2022 10:50:55 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:41610) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oedpJ-0001Qd-4T; Sat, 01 Oct 2022 10:50:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=M3QbPNTqr1jIZ7Vpo0IzMn+p9rWewpwLplxYy148mZI=; b=lzi+OgKTXTZr JFE6ImK/LfSErzcS88wxJsnvzJ65YrCQxEstNObZc1/h+LaW/Dk34D3E5jZQEwZe7nClGih1nrpRu 8l6b5CsbIa9zjhejQaihU5TibyMAjtlV1I2cTce9gnm7y44nfDBviJcjJpO9xQdrC0FQq9cf/osWf TQBSxBdrvmJuVWSNUTZ+7xrTcJkIYFAQjttEELtYAl6PWYJkf9OSfLmwF2h3N4Rx33FnlTEXKX4ee rzeAmrVKtWcMZpkR6mgpHg1SWwo/iMv+td9tN2RQqNQcFzlQWbcfZQKJtlYa0VboDDibRzl+/JW2j ZaSi0oW/skE5Ee731Iq+iw==; Received: from [87.69.77.57] (port=3818 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 1oedpH-0004kr-HV; Sat, 01 Oct 2022 10:50:48 -0400 Date: Sat, 01 Oct 2022 17:50:35 +0300 Message-Id: <83fsg7bnt0.fsf@gnu.org> From: Eli Zaretskii To: Stefan Kangas In-Reply-To: (message from Stefan Kangas on Sat, 1 Oct 2022 16:15:09 +0200) Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" References: X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58224 Cc: 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Stefan Kangas > Date: Sat, 1 Oct 2022 16:15:09 +0200 > > Every time I "make bootstrap", I get a ton of spurious messages (see > below). I believe they started showing up with Lars' much appreciated > work on improving build speeds. I have tripped myself up over this > more than once, and I suspect it will confuse users too. It's not spurious, it's because we deliberately fiddle with the time stamps to make sure *.elc files are used instead of *.el, to make the build faster. (This has nothing to do with what Lars did, it's due to changes by Alan to speedup the first stage of the bootstrap.) From debbugs-submit-bounces@debbugs.gnu.org Sat Oct 01 12:10:40 2022 Received: (at 58224) by debbugs.gnu.org; 1 Oct 2022 16:10:40 +0000 Received: from localhost ([127.0.0.1]:45604 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oef4a-0003VV-8J for submit@debbugs.gnu.org; Sat, 01 Oct 2022 12:10:40 -0400 Received: from mail-oo1-f42.google.com ([209.85.161.42]:42938) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oef4Y-0003VF-5P for 58224@debbugs.gnu.org; Sat, 01 Oct 2022 12:10:38 -0400 Received: by mail-oo1-f42.google.com with SMTP id r15-20020a4abf0f000000b004761c7e6be1so4207449oop.9 for <58224@debbugs.gnu.org>; Sat, 01 Oct 2022 09:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=/v1Mu3qgCREtobSCZdylwWiqVSCSOb/o1l8OKN8wrIk=; b=N/67vcAxkGivNtQK66bYN0hSbMppY342O3ps1CRsn7YTcwDEvMPyhjB8znjLiIX/hO h/CHUYU/L72jYManKPxMKEWz6L/7qfbuG2b6dSHsWhiOEG+k4fI8Ngw403rZCcPltLAV jXxkXDbj0xn5XqzPC1CwdX1qI8uqv9oGiZRPVrhEaaeLoGLwX7iT89ryMs9wMGztPmiV YorPLXKoGbbDt4+x0H5ka0zc2Yo8XoOeqnIc1za3ZjB7hIF3x/2NDVkOuucPWEsBb/yI tVbCmrmrU0PzQGhtSwSh9PRQTkVVhFIlU4KHdX+4oSSQhLMa9TarzBgr/c6y38oOZRqp 2Xug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=/v1Mu3qgCREtobSCZdylwWiqVSCSOb/o1l8OKN8wrIk=; b=iXHjhU8hj9aq8phHDh6/cZoA/KNKhLc8SLuW6pdHoZcU1jaVSJaqVRBP3mxPDeQQcD 99NkpjpyptOVrBG/ucaN1KQnrkYGpCUUXTygD1jdpn/URShxPJ7BhlF4thvfG4V+ePT8 D4Jx8wCHdWqH1dpzFte0zvWvX1ZmIxlzz6YwcgsaQ5+GApSsxy5RmyyKf5f9E2w2MfEq W1d0gfbCNi+UnD4fmDuiYTpiH8C7VjomdZZtYqnz059VhJhvDR+JeCHIn3lJ+sLHwhPI CxscSW2tw8bplz0Dl5vJKTH68WjhtbvIKdHcvoJiA6INpP2JxhJLOGm/4I1X41ltXW+v uMHw== X-Gm-Message-State: ACrzQf2x/SSuySgZBN3b5vh3HGpXWowgDLzLAJRoPBQTSK02ZTUBtc3i CFWfSCx1LpmV4nmo8/hL7bksxl9ZG4zA7HRvZyo= X-Google-Smtp-Source: AMsMyM5QMWR18mA5wUU1ua/SX/65M3g4QOoF5CG9RsQ+DXZ1TnmLdq7laxkOEBNYKr1EOgHE/qs2jUgAltBNWwdd8BQ= X-Received: by 2002:a4a:4bc5:0:b0:47d:9d6f:928b with SMTP id q188-20020a4a4bc5000000b0047d9d6f928bmr92591ooa.34.1664640632325; Sat, 01 Oct 2022 09:10:32 -0700 (PDT) MIME-Version: 1.0 References: <83fsg7bnt0.fsf@gnu.org> In-Reply-To: <83fsg7bnt0.fsf@gnu.org> From: Stefan Kangas Date: Sat, 1 Oct 2022 18:10:19 +0200 Message-ID: Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" To: Eli Zaretskii Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: Alan Mackenzie , 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Eli Zaretskii writes: > (This has nothing to do with what Lars did, it's due to changes by > Alan to speedup the first stage of the bootstrap.) Oh, right. I forgot about that. I'm copying in Alan, in case he has any comments. From debbugs-submit-bounces@debbugs.gnu.org Sat Oct 01 14:11:48 2022 Received: (at 58224) by debbugs.gnu.org; 1 Oct 2022 18:11:48 +0000 Received: from localhost ([127.0.0.1]:45677 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oegxo-0006Su-8u for submit@debbugs.gnu.org; Sat, 01 Oct 2022 14:11:48 -0400 Received: from mx3.muc.de ([193.149.48.5]:26906) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oegxm-0006Sg-FA for 58224@debbugs.gnu.org; Sat, 01 Oct 2022 14:11:47 -0400 Received: (qmail 63275 invoked by uid 3782); 1 Oct 2022 20:11:40 +0200 Received: from acm.muc.de (p4fe1535c.dip0.t-ipconnect.de [79.225.83.92]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 01 Oct 2022 20:11:40 +0200 Received: (qmail 7928 invoked by uid 1000); 1 Oct 2022 18:11:38 -0000 Date: Sat, 1 Oct 2022 18:11:38 +0000 To: Stefan Kangas Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83fsg7bnt0.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, Eli Zaretskii , 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, Stefan. On Sat, Oct 01, 2022 at 18:10:19 +0200, Stefan Kangas wrote: > Eli Zaretskii writes: > > (This has nothing to do with what Lars did, it's due to changes by > > Alan to speedup the first stage of the bootstrap.) > Oh, right. I forgot about that. > I'm copying in Alan, in case he has any comments. Well, my thoughts back when implementing that speedup were that the speedup was more important than a few irritating messages. I suppose that's becomng less true as the long delays from the past fade from memory. The particular message about " newer than byte-compile file; using older file" is hard-coded into Fload in src/lread.c. It was considered important enough to supersede the flag variable force-load-messages. It also supersedes the parameter NOMESSAGE to Fload. I don't know why this message is considered so important. Maybe we might reconsider its importance. But there are already two flag variables meant to control messages from Fload, so adding a third special one probably wouldn't be a good idea. This doesn't seem like an easy issue to resolve without nasty special case code. Either that, or we reconsider the mechanism of making the ..elc files older to trigger make's recompiling of the .el files to .eln. Maybe there's a better way of doing that. -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Sat Oct 01 17:15:58 2022 Received: (at 58224) by debbugs.gnu.org; 1 Oct 2022 21:15:58 +0000 Received: from localhost ([127.0.0.1]:45771 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oejq2-0002U9-9W for submit@debbugs.gnu.org; Sat, 01 Oct 2022 17:15:58 -0400 Received: from mx3.muc.de ([193.149.48.5]:31741) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oejpz-0002Tu-Vz for 58224@debbugs.gnu.org; Sat, 01 Oct 2022 17:15:56 -0400 Received: (qmail 21618 invoked by uid 3782); 1 Oct 2022 23:15:48 +0200 Received: from acm.muc.de (p4fe1535c.dip0.t-ipconnect.de [79.225.83.92]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sat, 01 Oct 2022 23:15:47 +0200 Received: (qmail 4855 invoked by uid 1000); 1 Oct 2022 21:15:46 -0000 Date: Sat, 1 Oct 2022 21:15:46 +0000 To: Stefan Kangas Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83fsg7bnt0.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, Eli Zaretskii , 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello again, Stefan. I've hacked a quick fix together. The idea is to give the variable force-load-messages an extra possibility, 'never. This suppresses the messages we want to suppress. No guarantees, but the patch is below, if you want to try it out. On Sat, Oct 01, 2022 at 18:11:38 +0000, Alan Mackenzie wrote: > Hello, Stefan. > On Sat, Oct 01, 2022 at 18:10:19 +0200, Stefan Kangas wrote: > > Eli Zaretskii writes: > > > (This has nothing to do with what Lars did, it's due to changes by > > > Alan to speedup the first stage of the bootstrap.) > > Oh, right. I forgot about that. > > I'm copying in Alan, in case he has any comments. > Well, my thoughts back when implementing that speedup were that the > speedup was more important than a few irritating messages. I suppose > that's becomng less true as the long delays from the past fade from > memory. > The particular message about " newer than byte-compile file; using > older file" is hard-coded into Fload in src/lread.c. It was considered > important enough to supersede the flag variable force-load-messages. It > also supersedes the parameter NOMESSAGE to Fload. > I don't know why this message is considered so important. Maybe we > might reconsider its importance. But there are already two flag > variables meant to control messages from Fload, so adding a third > special one probably wouldn't be a good idea. > This doesn't seem like an easy issue to resolve without nasty special > case code. Either that, or we reconsider the mechanism of making the > ..elc files older to trigger make's recompiling of the .el files to .eln. > Maybe there's a better way of doing that. diff --git a/lisp/Makefile.in b/lisp/Makefile.in index bcf4a3146d..8065487f59 100644 --- a/lisp/Makefile.in +++ b/lisp/Makefile.in @@ -70,7 +70,8 @@ BYTE_COMPILE_FLAGS = --eval "(setq load-prefer-newer t byte-compile-warnings 'all)" \ $(BYTE_COMPILE_EXTRA_FLAGS) # ... but we must prefer .elc files for those in the early bootstrap. -compile-first: BYTE_COMPILE_FLAGS = $(BYTE_COMPILE_EXTRA_FLAGS) +compile-first: BYTE_COMPILE_FLAGS = \ + --eval "(setq force-load-messages 'never)" $(BYTE_COMPILE_EXTRA_FLAGS) # Files to compile before others during a bootstrap. This is done to # speed up the bootstrap process. They're ordered by size, so we use diff --git a/src/lread.c b/src/lread.c index 51cbf811ba..1ae0f9c0cc 100644 --- a/src/lread.c +++ b/src/lread.c @@ -1451,7 +1451,9 @@ Return t if the file exists and loads successfully. */) newer = 1; /* If we won't print another message, mention this anyway. */ - if (!NILP (nomessage) && !force_load_messages) + if (!NILP (nomessage) && + (NILP (Vforce_load_messages) + || !EQ (Vforce_load_messages, Qnever))) { Lisp_Object msg_file; msg_file = Fsubstring (found, make_fixnum (0), make_fixnum (-1)); @@ -1476,7 +1478,9 @@ Return t if the file exists and loads successfully. */) } val = call4 (Vload_source_file_function, found, hist_file_name, NILP (noerror) ? Qnil : Qt, - (NILP (nomessage) || force_load_messages) ? Qnil : Qt); + (NILP (nomessage) || + (!NILP (Vforce_load_messages) && !EQ (Vforce_load_messages, Qnever))) + ? Qnil : Qt); return unbind_to (count, val); } } @@ -1529,7 +1533,8 @@ Return t if the file exists and loads successfully. */) if (! NILP (Vpurify_flag)) Vpreloaded_file_list = Fcons (Fpurecopy (file), Vpreloaded_file_list); - if (NILP (nomessage) || force_load_messages) + if (NILP (nomessage) + || (!NILP (Vforce_load_messages) && !EQ (Vforce_load_messages, Qnever))) { if (is_module) message_with_string ("Loading %s (module)...", file, 1); @@ -1602,7 +1607,9 @@ Return t if the file exists and loads successfully. */) saved_strings[i].size = 0; } - if (!noninteractive && (NILP (nomessage) || force_load_messages)) + if (!noninteractive && (NILP (nomessage) + || (!NILP (Vforce_load_messages) + && !EQ (Vforce_load_messages, Qnever)))) { if (is_module) message_with_string ("Loading %s (module)...done", file, 1); @@ -5601,10 +5608,13 @@ incompatible byte codes can make Emacs crash when it tries to execute them. */); load_dangerous_libraries = 0; - DEFVAR_BOOL ("force-load-messages", force_load_messages, - doc: /* Non-nil means force printing messages when loading Lisp files. + DEFVAR_LISP ("force-load-messages", Vforce_load_messages, + doc: /* t means force printing messages when loading Lisp files. +`never' means suppress all messages when loading Lisp files. nil means just print +certain "important" messages. + This overrides the value of the NOMESSAGE argument to `load'. */); - force_load_messages = 0; + Vforce_load_messages = Qnil; DEFVAR_LISP ("bytecomp-version-regexp", Vbytecomp_version_regexp, doc: /* Regular expression matching safe to load compiled Lisp files. @@ -5685,6 +5695,8 @@ that are loaded before your customizations are read! */); DEFSYM (Qdir_ok, "dir-ok"); DEFSYM (Qdo_after_load_evaluation, "do-after-load-evaluation"); + DEFSYM (Qnever, "never"); + staticpro (&read_objects_map); read_objects_map = Qnil; staticpro (&read_objects_completed); -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 01:59:32 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 05:59:32 +0000 Received: from localhost ([127.0.0.1]:46096 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oes0i-0007M5-GU for submit@debbugs.gnu.org; Sun, 02 Oct 2022 01:59:32 -0400 Received: from eggs.gnu.org ([209.51.188.92]:55928) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oes0h-0007Lq-Gl for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 01:59:32 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:40490) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oes0c-0001nI-8w; Sun, 02 Oct 2022 01:59:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=cFTyvX6MVjS5RAMqePy6rJV7dXD98lso73YlCvEKYyc=; b=e04uxcLmgHi3 vhl0dxUJSSQY4aB/4nbhE0Fk3+9/+SXLAbSOwd7mMeeV/oP8vK9zDmPz9+bvlR7/3ywDMa9x2Hfj+ Ewp83tlJskuWhsfqFo1gbVi6s3UUpbMaxiUmRRnuRitXItwqWMLExGcSuyuenrCEQphBnlCpm4JqE dvY+Ch/5J8XFlGHtNG/zPWRX6pWHKsy7sfey5uQKUL6nWsJmJSZR9TdBtrRrOQNl/mrn338s/n503 05Z1y4VAq03I67fpu9W61I5O2jRpeBqbIZPX13Px9C003iBVHPuqhuJvVO3Uoy/Q/VTk63GOIcDsm vZYfDe/4cWcvA283yvBSRg==; Received: from [87.69.77.57] (port=3599 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 1oes0b-0003gE-DV; Sun, 02 Oct 2022 01:59:26 -0400 Date: Sun, 02 Oct 2022 08:59:16 +0300 Message-Id: <83r0zqahqj.fsf@gnu.org> From: Eli Zaretskii To: Alan Mackenzie In-Reply-To: (message from Alan Mackenzie on Sat, 1 Oct 2022 21:15:46 +0000) Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" References: <83fsg7bnt0.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58224 Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > Date: Sat, 1 Oct 2022 21:15:46 +0000 > Cc: Eli Zaretskii , 58224@debbugs.gnu.org, acm@muc.de > From: Alan Mackenzie > > I've hacked a quick fix together. The idea is to give the variable > force-load-messages an extra possibility, 'never. This suppresses the > messages we want to suppress. Instead of inventing a new value that overrides the non-nil value, why not simply reset the variable to nil? From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 06:43:54 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 10:43:55 +0000 Received: from localhost ([127.0.0.1]:46327 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oewRu-0006AM-Jp for submit@debbugs.gnu.org; Sun, 02 Oct 2022 06:43:54 -0400 Received: from mx3.muc.de ([193.149.48.5]:52305) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oewRr-0006A8-L0 for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 06:43:52 -0400 Received: (qmail 94247 invoked by uid 3782); 2 Oct 2022 12:43:45 +0200 Received: from acm.muc.de (p2e5d502a.dip0.t-ipconnect.de [46.93.80.42]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 02 Oct 2022 12:43:45 +0200 Received: (qmail 3559 invoked by uid 1000); 2 Oct 2022 10:43:44 -0000 Date: Sun, 2 Oct 2022 10:43:44 +0000 To: Eli Zaretskii Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83r0zqahqj.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, Eli. On Sun, Oct 02, 2022 at 08:59:16 +0300, Eli Zaretskii wrote: > > Date: Sat, 1 Oct 2022 21:15:46 +0000 > > Cc: Eli Zaretskii , 58224@debbugs.gnu.org, acm@muc.de > > From: Alan Mackenzie > > I've hacked a quick fix together. The idea is to give the variable > > force-load-messages an extra possibility, 'never. This suppresses the > > messages we want to suppress. > Instead of inventing a new value that overrides the non-nil value, why > not simply reset the variable to nil? force-load-messages is nil by default, and currently isn't used at all by Emacs. It seems to be a pure debugging variable. The NOMESSAGE argument to Fload when non-nil, causes the unwanted message: Source file `foo.el' newer than byte-compiled file; using older file .. When NOMESSAGE is nil, we get instead Loading foo.elc (compiled; note, source file is newer)... .. Whichever setting of NOMESSAGE and force-load-messages we use, we get one of the above messages displayed. So, I'm proposing using a new value 'never for force-load-messages to mean display neither of these messages. -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 07:04:31 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 11:04:31 +0000 Received: from localhost ([127.0.0.1]:46333 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oewlq-0006hK-Lo for submit@debbugs.gnu.org; Sun, 02 Oct 2022 07:04:31 -0400 Received: from eggs.gnu.org ([209.51.188.92]:58420) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oewlk-0006h3-Kx for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 07:04:29 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:50472) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oewle-00078I-Mo; Sun, 02 Oct 2022 07:04:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=rfQtq2c9xy6HCZpCGC2/cIACIGClKa9wFqE2kcYN5sQ=; b=G4WpJmJrbfdt eamQzW+ke2su8xzFw/oSb8VPUahV/CH+Yop4rQQ8GEZjoxYo4R5Ayz/BFWssn0gCk666oPmbo69kG MUJaKowEIAag9SV/D3pon4Fod89RLlrj0JttW1M/rb8UIYhwkNKX4J6QDY5Lvldn3E300mdp+vPzI YFGd9UFyQFcBN7T5JEHDkdKmUx8u2k8b7SlxK8FBr3ZG+lI3Oto376FEEbpoY7DjiPMH8F3GXEQ67 gCb5yPo3qGwPbVv5/Cc5f/r/HATYEDXcIwvuPnJoiVJ2r2HhNhmbhG2gGgiNV8qB4lUNMiixA1aqX Ycku3jsmDiIRiBW/Ip3qbg==; Received: from [87.69.77.57] (port=4177 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 1oewle-00086B-5t; Sun, 02 Oct 2022 07:04:18 -0400 Date: Sun, 02 Oct 2022 14:04:08 +0300 Message-Id: <83y1ty1o7r.fsf@gnu.org> From: Eli Zaretskii To: Alan Mackenzie In-Reply-To: (message from Alan Mackenzie on Sun, 2 Oct 2022 10:43:44 +0000) Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > Date: Sun, 2 Oct 2022 10:43:44 +0000 > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org, acm@muc.de > From: Alan Mackenzie > > > Instead of inventing a new value that overrides the non-nil value, why > > not simply reset the variable to nil? > > force-load-messages is nil by default, and currently isn't used at all > by Emacs. It seems to be a pure debugging variable. > > The NOMESSAGE argument to Fload when non-nil, causes the unwanted > message: > > Source file `foo.el' newer than byte-compiled file; using older file > > .. When NOMESSAGE is nil, we get instead > > Loading foo.elc (compiled; note, source file is newer)... > > .. Whichever setting of NOMESSAGE and force-load-messages we use, we get > one of the above messages displayed. So, I'm proposing using a new > value 'never for force-load-messages to mean display neither of these > messages. I don't want to complicate the public Lisp API because we have a singular situation at some point of the bootstrap, and for minor aesthetic reasons at that; that is the tail wagging the dog. So let's fix this more subtly. How about recognizing (inside Fload) a specific time stamp of the older file we use (we set it to the beginning of the Epoch, right?), and suppressing the message in that case? From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 07:32:39 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 11:32:39 +0000 Received: from localhost ([127.0.0.1]:46362 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oexD5-000198-Gs for submit@debbugs.gnu.org; Sun, 02 Oct 2022 07:32:39 -0400 Received: from mx3.muc.de ([193.149.48.5]:53591) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oexD3-00018u-W9 for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 07:32:38 -0400 Received: (qmail 90545 invoked by uid 3782); 2 Oct 2022 13:32:30 +0200 Received: from acm.muc.de (p2e5d502a.dip0.t-ipconnect.de [46.93.80.42]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 02 Oct 2022 13:32:30 +0200 Received: (qmail 18875 invoked by uid 1000); 2 Oct 2022 11:32:29 -0000 Date: Sun, 2 Oct 2022 11:32:29 +0000 To: Eli Zaretskii Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83y1ty1o7r.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, Eli. On Sun, Oct 02, 2022 at 14:04:08 +0300, Eli Zaretskii wrote: > > Date: Sun, 2 Oct 2022 10:43:44 +0000 > > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org, acm@muc.de > > From: Alan Mackenzie > > > Instead of inventing a new value that overrides the non-nil value, why > > > not simply reset the variable to nil? > > force-load-messages is nil by default, and currently isn't used at all > > by Emacs. It seems to be a pure debugging variable. > > The NOMESSAGE argument to Fload when non-nil, causes the unwanted > > message: > > Source file `foo.el' newer than byte-compiled file; using older file > > .. When NOMESSAGE is nil, we get instead > > Loading foo.elc (compiled; note, source file is newer)... > > .. Whichever setting of NOMESSAGE and force-load-messages we use, we get > > one of the above messages displayed. So, I'm proposing using a new > > value 'never for force-load-messages to mean display neither of these > > messages. > I don't want to complicate the public Lisp API because we have a > singular situation at some point of the bootstrap, and for minor > aesthetic reasons at that; that is the tail wagging the dog. So let's > fix this more subtly. I agree. > How about recognizing (inside Fload) a specific time stamp of the > older file we use (we set it to the beginning of the Epoch, right?), > and suppressing the message in that case? :-) That's a nice idea. I'll see if I can get that done today. Thanks! -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 11:38:34 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 15:38:34 +0000 Received: from localhost ([127.0.0.1]:47854 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of134-0003gI-CK for submit@debbugs.gnu.org; Sun, 02 Oct 2022 11:38:34 -0400 Received: from mx3.muc.de ([193.149.48.5]:60172) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of132-0003g2-OQ for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 11:38:33 -0400 Received: (qmail 49001 invoked by uid 3782); 2 Oct 2022 17:38:25 +0200 Received: from acm.muc.de (p2e5d502a.dip0.t-ipconnect.de [46.93.80.42]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 02 Oct 2022 17:38:25 +0200 Received: (qmail 4341 invoked by uid 1000); 2 Oct 2022 15:38:25 -0000 Date: Sun, 2 Oct 2022 15:38:25 +0000 To: Eli Zaretskii Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83y1ty1o7r.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, Eli. On Sun, Oct 02, 2022 at 14:04:08 +0300, Eli Zaretskii wrote: > > Date: Sun, 2 Oct 2022 10:43:44 +0000 > > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org, acm@muc.de > > From: Alan Mackenzie > > > Instead of inventing a new value that overrides the non-nil value, why > > > not simply reset the variable to nil? > > force-load-messages is nil by default, and currently isn't used at all > > by Emacs. It seems to be a pure debugging variable. > > The NOMESSAGE argument to Fload when non-nil, causes the unwanted > > message: > > Source file `foo.el' newer than byte-compiled file; using older file > > .. When NOMESSAGE is nil, we get instead > > Loading foo.elc (compiled; note, source file is newer)... > > .. Whichever setting of NOMESSAGE and force-load-messages we use, we get > > one of the above messages displayed. So, I'm proposing using a new > > value 'never for force-load-messages to mean display neither of these > > messages. > I don't want to complicate the public Lisp API because we have a > singular situation at some point of the bootstrap, and for minor > aesthetic reasons at that; that is the tail wagging the dog. So let's > fix this more subtly. > How about recognizing (inside Fload) a specific time stamp of the > older file we use (we set it to the beginning of the Epoch, right?), > and suppressing the message in that case? I've got this working, but .... In lread.c I've got: struct timespec epoch_timespec = {(time_t)0, 0}; /* 1970-01-01T00:00 UTC */ , which clearly isn't 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. Thanks! -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 11:54:27 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 15:54:27 +0000 Received: from localhost ([127.0.0.1]:47864 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of1IR-00046V-D8 for submit@debbugs.gnu.org; Sun, 02 Oct 2022 11:54:27 -0400 Received: from eggs.gnu.org ([209.51.188.92]:33568) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of1IP-00046H-Cr for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 11:54:25 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:55794) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of1IJ-0000kf-VK; Sun, 02 Oct 2022 11:54:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=PwD/bohc9pyAtA2gCeCJ9hsdoiq7tgrSSjTlKpopwe0=; b=e4yvaZAZx8kw G3Xj87LoUW3JAhxKIWWaJrPiMFxsS6npKon4/jhNk6VXcHOqy7j62HuqYaBAdXeEn0dsUkTU7Rd0P qByO79mIuG01sbK6kQO/qIpXKm2ojm4pPEwxdvG+nwf4CZSlG9jqy5+KwW/kk0G7m95SSGJCnIq2m XXIDecWS7UsNgHB/4jA0swIqly6RHQlUCP8+JiRW9HC5JhsFOyWz1SVN8WKkEUPQ8zJUqPhR1d0Bd TlQ76A/XQcnEBc0IvxJPWqlRCU5qqPgUr3ja72NdGS8rbwpFJEiDuJSmscxf3eW0R8+ertjhBu0HG TYn9QN7C4wyVGKEe6Rbrbw==; Received: from [87.69.77.57] (port=2469 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 1of1IJ-0000Yp-E5; Sun, 02 Oct 2022 11:54:19 -0400 Date: Sun, 02 Oct 2022 18:54:10 +0300 Message-Id: <83k05i1asd.fsf@gnu.org> From: Eli Zaretskii To: Alan Mackenzie In-Reply-To: (message from Alan Mackenzie on Sun, 2 Oct 2022 15:38:25 +0000) Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58224 Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > Date: Sun, 2 Oct 2022 15:38:25 +0000 > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org > From: Alan Mackenzie > > 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? From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 12:46:10 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 16:46:10 +0000 Received: from localhost ([127.0.0.1]:47899 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of26U-0007b8-H6 for submit@debbugs.gnu.org; Sun, 02 Oct 2022 12:46:10 -0400 Received: from mx3.muc.de ([193.149.48.5]:62107) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of26S-0007al-NE for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 12:46:09 -0400 Received: (qmail 88764 invoked by uid 3782); 2 Oct 2022 18:46:02 +0200 Received: from acm.muc.de (p2e5d502a.dip0.t-ipconnect.de [46.93.80.42]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 02 Oct 2022 18:46:01 +0200 Received: (qmail 4794 invoked by uid 1000); 2 Oct 2022 16:46:01 -0000 Date: Sun, 2 Oct 2022 16:46:01 +0000 To: Eli Zaretskii Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> <83k05i1asd.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83k05i1asd.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, Eli. On Sun, Oct 02, 2022 at 18:54:10 +0300, Eli Zaretskii wrote: > > Date: Sun, 2 Oct 2022 15:38:25 +0000 > > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org > > From: Alan Mackenzie > > 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? Don't we build for operating systems with different epochs? > > 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? Yes thanks! But it's horribly complicated, involving wierd readings and settings of the TZ environment variable, and so on. If a binary zero time would do (as above), maybe it would be satisfactory. ;-) -- Alan Mackenzie (Nuremberg, Germany). From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 13:07:43 2022 Received: (at 58224) by debbugs.gnu.org; 2 Oct 2022 17:07:43 +0000 Received: from localhost ([127.0.0.1]:47928 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of2RL-0008Bz-Gw for submit@debbugs.gnu.org; Sun, 02 Oct 2022 13:07:43 -0400 Received: from eggs.gnu.org ([209.51.188.92]:37804) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of2RJ-0008Bn-DV for 58224@debbugs.gnu.org; Sun, 02 Oct 2022 13:07:41 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:43134) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of2RC-0002fF-If; Sun, 02 Oct 2022 13:07:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=fHYeHHMK5vId2Nacn5P5ODrDsQAYSoZoLBPUn7QauqQ=; b=icekyB4N9em7 Wy7FLuqvN+YEO8sD2WKmvkLDRKoxX9mGp5/FFf3PZteYnuzjDKoRdRruL8D1seF8jzbZhjLwnwyYv h0tvfS71/B6AcsbwTfKIZJKzYiN6Xg7dOO5MNK5AUw60DT1xH76u0+C9uOWyO59PLAFMO3bF5cLgb LZybBnE8IZqOBr+QD/JrIPwYjVGRt71zpTtOqKuElOMJ9M2f+SMlAPbZCryYzkuzy4KSZEqF801yW OsnB1QLYLgJQokM0aQ52hRF4FR0c5YCJ4wl3SQsGKnddN/qLoirjZfPrvBZMdG5HjRSdbbyWICGwg MawKoAvrImRjrICQfKvIxA==; Received: from [87.69.77.57] (port=3016 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 1of2RC-0002Cg-15; Sun, 02 Oct 2022 13:07:34 -0400 Date: Sun, 02 Oct 2022 20:07:26 +0300 Message-Id: <838rly17e9.fsf@gnu.org> From: Eli Zaretskii To: Alan Mackenzie In-Reply-To: (message from Alan Mackenzie on Sun, 2 Oct 2022 16:46:01 +0000) Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" References: <83fsg7bnt0.fsf@gnu.org> <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> <83k05i1asd.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 58224 Cc: acm@muc.de, stefankangas@gmail.com, 58224@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > Date: Sun, 2 Oct 2022 16:46:01 +0000 > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org, acm@muc.de > From: Alan Mackenzie > > > > 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? > > Don't we build for operating systems with different epochs? No, the Epoch is the same for everyone. It's a Posix notion, AFAIK. > > Is mktime the function you are after? > > Yes thanks! But it's horribly complicated, involving wierd readings and > settings of the TZ environment variable, and so on. Not if you are interested in UTC. > If a binary zero time would do (as above), maybe it would be > satisfactory. ;-) Yes. From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 16:37:24 2022 Received: (at 58224-done) by debbugs.gnu.org; 2 Oct 2022 20:37:24 +0000 Received: from localhost ([127.0.0.1]:48163 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of5iG-0005QB-An for submit@debbugs.gnu.org; Sun, 02 Oct 2022 16:37:24 -0400 Received: from mx3.muc.de ([193.149.48.5]:13401) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of5iE-0005Py-2p for 58224-done@debbugs.gnu.org; Sun, 02 Oct 2022 16:37:23 -0400 Received: (qmail 77072 invoked by uid 3782); 2 Oct 2022 22:37:15 +0200 Received: from acm.muc.de (p2e5d502a.dip0.t-ipconnect.de [46.93.80.42]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 02 Oct 2022 22:37:15 +0200 Received: (qmail 8065 invoked by uid 1000); 2 Oct 2022 20:37:14 -0000 Date: Sun, 2 Oct 2022 20:37:14 +0000 To: Eli Zaretskii , stefankangas@gmail.com Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Message-ID: References: <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> <83k05i1asd.fsf@gnu.org> <838rly17e9.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <838rly17e9.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224-done Cc: acm@muc.de, 58224-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Hello, Eli and Stefan. On Sun, Oct 02, 2022 at 20:07:26 +0300, Eli Zaretskii wrote: > > Date: Sun, 2 Oct 2022 16:46:01 +0000 > > Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org, acm@muc.de > > From: Alan Mackenzie > > > > 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? > > Don't we build for operating systems with different epochs? > No, the Epoch is the same for everyone. It's a Posix notion, AFAIK. > > > Is mktime the function you are after? > > Yes thanks! But it's horribly complicated, involving wierd readings and > > settings of the TZ environment variable, and so on. > Not if you are interested in UTC. > > If a binary zero time would do (as above), maybe it would be > > satisfactory. ;-) > Yes. OK, that's great! I've committed a patch, and I'm closing the bug with this post. -- Alan Mackenzie (Nuremberg, Germanay). From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 02 17:29:46 2022 Received: (at 58224-done) by debbugs.gnu.org; 2 Oct 2022 21:29:46 +0000 Received: from localhost ([127.0.0.1]:48219 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of6Wv-0006lK-QS for submit@debbugs.gnu.org; Sun, 02 Oct 2022 17:29:46 -0400 Received: from mail-oo1-f42.google.com ([209.85.161.42]:46592) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1of6Wt-0006l7-E0 for 58224-done@debbugs.gnu.org; Sun, 02 Oct 2022 17:29:44 -0400 Received: by mail-oo1-f42.google.com with SMTP id r136-20020a4a378e000000b004755953bc6cso5650298oor.13 for <58224-done@debbugs.gnu.org>; Sun, 02 Oct 2022 14:29:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date; bh=+8q7UcT+L/JDrotTn0IaPcdXmHQhox3o5bsuLt8x9T8=; b=l7Jm4Ud3ve3ojqjPHA8RyZkuIEnWTYf7eBpkpSr4BftLHLizvy0EZRhhYNOW/UNF8t dmHyDBssSpA/EDMEXAK3piKctllya+cSJTxmHT/OWXyrQ8vfHb18gmV43DotPCqDunrC O6BDBqHl+k9F9pvtB07r8vyyN0++CH2K0JVu1HLjMCw9MbAcWnZ5EqffJROH6kGtT7cI AceBorPwU3R5yfPfnwQ6e5CQPmj/udQq7pTlJc/LNDmbQrVa/9AsaksCPTyi63NVQK1i 7ufJCHmOfXaxSLobvGybqUPFqHDz5lnUvftMVK7wDNg7SqO1Ea8XLXBhLo/XHA5jp/0+ hgKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date; bh=+8q7UcT+L/JDrotTn0IaPcdXmHQhox3o5bsuLt8x9T8=; b=k1A33lBsEGdwOSvOpoKCNFWRu4lcgXGPd5p213Q1OP7invnbjgysFzMhk1mPBc5L8G YcWMGx1o+Yr8zQlqoHonWDqC1Vr+SnD6sziBp/7pWFvDjpaf6yU72fgHkl8xctLhNEWS LLrM5aVuH7Ntf/qiZ5sQbHgrN4cQghR46dEsr0MSKxkgg9nM9bIhOede+eP8GAnJY6Gc yvSXnxsbqu0uyQATKbDvgenQc5+KSdn21w1Oi0CIIj1ZCasQ0FlKNN7I6h9k1vaRQnnT Z2eXI0n4MdKvQg7xPZbTe3QCZPiT/PzSdtoj0UwXaU0itD6sFXx60roULJsackm4TOVe SnDg== X-Gm-Message-State: ACrzQf3B6vYvCX2mvLKeT/j1gjWOB8xk4VhO/eJ2r9h7DFfvbYQQIE/5 ZHy19LiojLN5uwPgZQQEMtGH7RZyQdkOsiDIuN8= X-Google-Smtp-Source: AMsMyM75qbr9Or+YiHz/qTlEldGSO6dxK5QKJCx2aPfXRhWtn/J95vAqlSrkf611lM4yZ4cAL93bJV5ztwKF/gJlJq0= X-Received: by 2002:a4a:4bc5:0:b0:47d:9d6f:928b with SMTP id q188-20020a4a4bc5000000b0047d9d6f928bmr1600001ooa.34.1664746177562; Sun, 02 Oct 2022 14:29:37 -0700 (PDT) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sun, 2 Oct 2022 23:29:36 +0200 From: Stefan Kangas In-Reply-To: References: <83r0zqahqj.fsf@gnu.org> <83y1ty1o7r.fsf@gnu.org> <83k05i1asd.fsf@gnu.org> <838rly17e9.fsf@gnu.org> X-Hashcash: 1:20:221002:acm@muc.de::yZb11FxaovcVM+7U:7D53 MIME-Version: 1.0 Date: Sun, 2 Oct 2022 23:29:36 +0200 Message-ID: Subject: Re: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" To: Alan Mackenzie , Eli Zaretskii Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 58224-done Cc: 58224-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Alan Mackenzie writes: > I've committed a patch, and I'm closing the bug with this post. Thanks! It works great. From unknown Thu Jul 17 20:12:57 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Mon, 31 Oct 2022 11:24:04 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator