From: Madhu <enometh@meer.net>
To: emacs-devel@gnu.org
Subject: Re: Org mode update breaking build?
Date: Mon, 08 May 2023 17:30:17 +0530 [thread overview]
Message-ID: <m3wn1jnicu.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: ZFKEC4EoYZeTjOhK@ACM
* Alan Mackenzie <ZFKEC4EoYZeTjOhK@ACM> :
Wrote on Wed, 3 May 2023 15:55:55 +0000:
> On Wed, May 03, 2023 at 17:26:05 +0200, Tobias Bading wrote:
>> Grrr. Is it normal that Org updates break builds?
> For me, it has become normal. I'm not happy about it.
> I don't use org, and I don't understand why I should be expected to
> debug its breaking of the build.
>
> In practice, I have to do make bootstrap every time I update my
> repositories.
I haven't update master very recently but a while ago I got into the
habit of running a script before calling `make'. the $1 parameter is the
path to src/lisp. it lists stale elc files, which I then delete by hand.
```
for i in $(find "$1" -name \*.elc); do
j=${i%c};
if [ ! -e "$i" ]; then
echo "MISSING $i" >> /dev/stderr
elif [ ! -e "$j" ]; then
echo "MISSING $j" >> /dev/stderr
else
# file-newer-p.sh $j $i # UNTESTED.
a=$(stat -c '%Y' "$j")
b=$(stat -c '%Y' "$i")
if [ $a -gt $a ]; then echo "$i"; fi;
fi
done
```
Since I started doing this, I don't think I've faced elisp recompilation
problems. But I never understood the rationale for "loading stale elc"
behaviour as a part of recompilation. If someone can explain that I'd
appreciate it.
next prev parent reply other threads:[~2023-05-08 12:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 15:26 Org mode update breaking build? Tobias Bading
2023-05-03 15:55 ` Alan Mackenzie
2023-05-03 16:11 ` Tobias Bading
2023-05-03 16:58 ` Eli Zaretskii
2023-05-03 17:02 ` Tobias Bading
2023-05-04 4:42 ` Po Lu
2023-05-04 5:48 ` Eli Zaretskii
2023-05-09 16:34 ` Sam Steingold
2023-05-09 16:47 ` Eli Zaretskii
2023-05-09 17:17 ` Sam Steingold
2023-05-09 19:07 ` Eli Zaretskii
2023-05-10 18:12 ` Sam Steingold
2023-05-08 12:00 ` Madhu [this message]
2023-05-08 13:22 ` Eli Zaretskii
2023-05-14 5:49 ` Madhu
2023-05-14 5:59 ` Eli Zaretskii
2023-05-03 16:04 ` Eli Zaretskii
2023-05-03 16:07 ` Tobias Bading
2023-05-03 16:57 ` Eli Zaretskii
2023-05-03 18:56 ` John ff
2023-05-03 19:02 ` Tassilo Horn
2023-05-04 2:00 ` Michael Heerdegen
2023-05-04 3:23 ` Bob Rogers
2023-05-04 3:30 ` Michael Heerdegen
2023-05-04 3:44 ` Bob Rogers
2023-05-04 5:42 ` Eli Zaretskii
2023-05-04 5:58 ` Bob Rogers
2023-05-04 5:41 ` Eli Zaretskii
2023-05-04 5:13 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wn1jnicu.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).