From: John ff <jpff@codemist.co.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tobias Bading <tbading@web.de>,emacs-devel <emacs-devel@gnu.org>
Subject: Re: Org mode update breaking build?
Date: Wed, 03 May 2023 19:56:21 +0100 [thread overview]
Message-ID: <16785527-b6fb-4ecc-9054-eaa1aa3c61ab@codemist.co.uk> (raw)
In-Reply-To: <83wn1pl5ek.fsf@gnu.org>
On 3 May 2023, 17:58, at 17:58, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 3 May 2023 18:07:27 +0200
>> Cc: emacs-devel@gnu.org
>> From: Tobias Bading <tbading@web.de>
>>
>> On 03.05.23 18:04, Eli Zaretskii wrote:
>> > Yes, on emacs-29. Well, not "normal" but "expected". The fix is
>to
>> > remove lisp/org/*.elc and say "make" again.
>>
>> “make distclean” didn’t help and no *.elc should have survived that,
>right?
>
>Wrong. "make distclean" doesn't remove any *.elc files, because those
>come with the tarball, and "make distclean" only removes stuff that
>didn't come with the tarball, but was built later.
next prev parent reply other threads:[~2023-05-03 18:56 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
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 [this message]
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=16785527-b6fb-4ecc-9054-eaa1aa3c61ab@codemist.co.uk \
--to=jpff@codemist.co.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tbading@web.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 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).