From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.bugs Subject: bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer` Date: Sat, 16 Nov 2024 18:11:01 +0300 Message-ID: <6bc3a410f0857c3e3433070ac19deaf7eae88c63.camel@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21428"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.54.1 Cc: Alan Mackenzie To: 74382@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 16 16:12:30 2024 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 1tCKTN-0005RK-C7 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 16 Nov 2024 16:12:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tCKSz-0004UC-E8; Sat, 16 Nov 2024 10:12:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tCKSx-0004Tz-4W for bug-gnu-emacs@gnu.org; Sat, 16 Nov 2024 10:12:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tCKSw-0001iq-SC for bug-gnu-emacs@gnu.org; Sat, 16 Nov 2024 10:12:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:Date:From:To:Subject; bh=pil43Wrexx6kdt3rM6HaggCczjQAXL6rduH8BJEsEIw=; b=PLqev7TKiYbNBuql48nzP8w7ha3TbJFuRi6XEOOrjLMszRMZMdCSQtWkBTuXKiSPaUFo/DOgsKA8r9eghtE2vmba/b5Mg78+xKRjErZroSDVxcY6ECUsZHSfIcV/iPLQpPIeq1lAWrxTzUl4FASpbW0eLPOtAUCYlGSevLzEDkBOOZSsws92AulFTDk7N6Y5uyqvzs1GK/ZKfr7wc1WtxDmLn/Xgp8Cmkh+kYVQLG24imGIjkMq4RTifKk9nAuMXHrkiz85sqdiJMGPC7QwLoQWKHROeFp2TYzOXSPhMH3UueYuT5iUDv85i3+/xKHa4GXF8byQcFP8CDhGHII00KA==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tCKSw-00081H-H5 for bug-gnu-emacs@gnu.org; Sat, 16 Nov 2024 10:12:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Konstantin Kharlamov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 16 Nov 2024 15:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 74382 X-GNU-PR-Package: emacs X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.173176988030748 (code B ref -1); Sat, 16 Nov 2024 15:12:02 +0000 Original-Received: (at submit) by debbugs.gnu.org; 16 Nov 2024 15:11:20 +0000 Original-Received: from localhost ([127.0.0.1]:54343 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tCKSG-0007zs-BB for submit@debbugs.gnu.org; Sat, 16 Nov 2024 10:11:20 -0500 Original-Received: from lists.gnu.org ([209.51.188.17]:38510) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tCKSC-0007zi-3V for submit@debbugs.gnu.org; Sat, 16 Nov 2024 10:11:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tCKSB-0004Se-2P for bug-gnu-emacs@gnu.org; Sat, 16 Nov 2024 10:11:15 -0500 Original-Received: from forward100b.mail.yandex.net ([2a02:6b8:c02:900:1:45:d181:d100]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tCKS8-0001Hw-A8 for bug-gnu-emacs@gnu.org; Sat, 16 Nov 2024 10:11:14 -0500 Original-Received: from mail-nwsmtp-smtp-production-main-36.sas.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-36.sas.yp-c.yandex.net [IPv6:2a02:6b8:c24:18aa:0:640:5723:0]) by forward100b.mail.yandex.net (Yandex) with ESMTPS id 717D060D1E; Sat, 16 Nov 2024 18:11:03 +0300 (MSK) Original-Received: by mail-nwsmtp-smtp-production-main-36.sas.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id 2BQOnoKOdCg0-UfhnlZZr; Sat, 16 Nov 2024 18:11:02 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1731769863; bh=pil43Wrexx6kdt3rM6HaggCczjQAXL6rduH8BJEsEIw=; h=Date:Cc:To:From:Subject:Message-ID; b=epJV95KIzm/y5prCNTqcjOMe4ya0EGwmdMBmiBvV+zHm3VDpsj47Y1Si3CI+Qlhft vQw7otMpPi/YdoKkpV55KpZ3nhcvNTWYDdzxINdVKJ6MOxHNpPDS8KkXDbXpu0NQJ8 MEeENk0mDftdokg7Xq7g+oaoV3nkqsBSuGr7aH6I= Authentication-Results: mail-nwsmtp-smtp-production-main-36.sas.yp-c.yandex.net; dkim=pass header.i=@yandex.ru Received-SPF: pass client-ip=2a02:6b8:c02:900:1:45:d181:d100; envelope-from=Hi-Angel@yandex.ru; helo=forward100b.mail.yandex.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:295466 Archived-At: CC: Alan Mackenzie, author of the change in 10083e788f7349fa363d100687dc3d9= 4bea88f57 I've seen for a long time Emacs master builds fail from time to time in spe= ctacular ways after updating the repo, sometimes so badly that `make clean` doesn't = help. I never dug into that though, but I'm attributing this to the occasional bu= ild messages similar to: Source file =E2=80=98/home/constantine/Projects/emacs/lisp/emacs-lisp/c= omp.el=E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/home/constantine/Projects/emacs/lisp/emacs-lisp/b= ytecomp.el=E2=80=99 newer than byte-compiled file; using older file Source file =E2=80=98/home/constantine/Projects/emacs/lisp/emacs-lisp/c= omp-cstr.el=E2=80=99 newer than byte-compiled file; using older file =E2=80=A6which makes sense, because if the repo changed `comp.el` API and E= macs during the build of newer files is trying to make use of older `.elc` file and hence t= he older API, it may result in failure. Got some spare time today, dug into one of the messages. From what I unders= tand it's caused by this line `lisp/Makefile.in`: # ... but we must prefer .elc files for those in the early bootstrap. compile-first: BYTE_COMPILE_FLAGS =3D $(BYTE_COMPILE_EXTRA_FLAGS) >From what I understand, this rewrites BYTE_COMPILE_FLAGS to be an empty var= iable, which results in `(setq load-prefer-newer t)` being stripped off of the bui= ld. The straightforward solution is to remove this line. But since the line's c= ommentary opposes to such solution, I'm starting up a discussion what exactly should = be the behavior here =F0=9F=98=8A