From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Konstantin Kharlamov <Hi-Angel@yandex.ru>
Cc: Alan Mackenzie <acm@muc.de>, 74382@debbugs.gnu.org
Subject: bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer`
Date: Sun, 17 Nov 2024 08:25:12 +0100 [thread overview]
Message-ID: <m2ldxi1fvr.fsf@gmail.com> (raw)
In-Reply-To: <b225b9d64035be6fc7e2f5a8d07ad4239d7031f1.camel@yandex.ru> (Konstantin Kharlamov's message of "Sat, 16 Nov 2024 20:45:47 +0300")
Konstantin Kharlamov <Hi-Angel@yandex.ru> writes:
> Sure, I just reproduced it after removing all `.elc` files in the repo,
> here how:
>
> 1. `git checkout f2f13fa630b` (a commit from April)
> 2. `make -j$(nproc)` to compile. Note: you don't need to wait for build
> to finish, I just waited for all files under `lisp/emacs-lisp`
> directory to finish compilation, and then ^C'ed it.
> 3. `git checkout 29098a291f5` (a November commit).
> 4. `make -j$(nproc)`
This would always work if lisp/Makefile would rm the .elc files from
COMPILE_FIRST, right? I suspect this isn't done to speed up the build in
the usual case, and because it's a bit difficult to automatically
determine if it has to done or not.
Does a "make clean" after the checkout in (3) make it work?
next prev parent reply other threads:[~2024-11-17 7:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 15:11 bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer` Konstantin Kharlamov
2024-11-16 16:27 ` Eli Zaretskii
2024-12-11 11:19 ` Konstantin Kharlamov
2024-12-11 15:41 ` Eli Zaretskii
2024-12-11 11:21 ` Konstantin Kharlamov
2024-11-16 16:53 ` Alan Mackenzie
2024-11-16 17:45 ` Konstantin Kharlamov
2024-11-16 18:38 ` Eli Zaretskii
2024-11-16 18:43 ` Konstantin Kharlamov
2024-11-16 20:00 ` Eli Zaretskii
2024-11-16 22:54 ` Konstantin Kharlamov
2024-11-17 6:44 ` Eli Zaretskii
2024-11-17 15:31 ` Konstantin Kharlamov
2024-11-17 7:25 ` Gerd Möllmann [this message]
2024-11-17 15:21 ` Konstantin Kharlamov
2024-11-17 15:37 ` Eli Zaretskii
2024-11-17 15:43 ` Konstantin Kharlamov
2024-11-17 15:53 ` Eli Zaretskii
2024-11-17 16:04 ` Konstantin Kharlamov
2024-11-17 16:29 ` Eli Zaretskii
2024-11-17 16:46 ` Konstantin Kharlamov
2024-11-17 17:09 ` Eli Zaretskii
2024-11-17 17:24 ` Konstantin Kharlamov
2024-11-18 4:06 ` Gerd Möllmann
2024-11-18 6:19 ` Konstantin Kharlamov
2024-11-18 10:05 ` Konstantin Kharlamov
2024-11-18 12:59 ` Eli Zaretskii
2024-11-18 13:12 ` Konstantin Kharlamov
2024-11-18 13:38 ` Eli Zaretskii
2024-12-07 11:58 ` Eli Zaretskii
2024-11-17 15:43 ` Gerd Möllmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ldxi1fvr.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74382@debbugs.gnu.org \
--cc=Hi-Angel@yandex.ru \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.