unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tobias Bading <tbading@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: Org mode update breaking build?
Date: Wed, 03 May 2023 19:04:12 +0300	[thread overview]
Message-ID: <83y1m5l7ur.fsf@gnu.org> (raw)
In-Reply-To: <00b52cc1-b0ac-a0c0-c91d-33a7213e9881@web.de> (message from Tobias Bading on Wed, 3 May 2023 17:26:05 +0200)

> Date: Wed, 3 May 2023 17:26:05 +0200
> From: Tobias Bading <tbading@web.de>
> 
> Warning (emacs): Org version mismatch.  Org loading aborted.
> This warning usually appears when a built-in Org version is loaded
> prior to the more recent Org version.
> 
> Version mismatch is commonly encountered in the following situations:
> 
> […]
> 
> In toplevel form:
> org/ob-core.el:31:2: Error: Org version mismatch.  Make sure that correct ‘load-path’ is set early in init.el
> make[3]: *** [Makefile:332: org/ob-core.elc] Error 1
> make[3]: *** Waiting for unfinished jobs....
> 
> --- >% ---
> 
> A “git clean -fdx -e .ccls-cache -e compile_commands.json -e TAGS” plus
> “./autogen.sh” plus “configure […]” plus “nice make -j4” later I have a
> working clean Emacs 29 again.
> 
> But of course the same happens again in my hacked worktree. So this time I
> try “make distclean” for a change — plus the whole autogen, configure,
> make aria again. And guess what… the error is still there!
> 
> Is that normal?

Yes, on emacs-29.  Well, not "normal" but "expected".  The fix is to
remove lisp/org/*.elc and say "make" again.

There's a solution on master, and an improvement on that solution in
the works, but I decided not to risk that on the release branch, since
the problem happens relatively rarely and the workaround is simple
enough.



  parent reply	other threads:[~2023-05-03 16:04 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 [this message]
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=83y1m5l7ur.fsf@gnu.org \
    --to=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).