unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "l@tlo" <lists@traduction-libre.org>
To: emacs-devel@gnu.org
Subject: "Org version mismatch." when building emacs
Date: Fri, 5 May 2023 10:47:40 +0900	[thread overview]
Message-ID: <C74BDDA2-777C-4420-B85C-1274CEB88E41@traduction-libre.org> (raw)

I just pulled the code in master, did ./autogen.sh and ./configure to be on the safe side and "make" gives me this:

org/ox-texinfo.el:33:2: Error: Org version mismatch.  Make sure that correct ‘load-path’ is set early in init.el
make[3]: *** [org/ox-texinfo.elc] Error 1
make[2]: *** [main-first] Error 2
make[1]: *** [lisp] Error 2

I read the explanations given with the error message:

> Version mismatch is commonly encountered in the following situations:
> 
> 1. Emacs is loaded using literate Org config and more recent Org
>    version is loaded inside the file loaded by ‘org-babel-load-file’.
>    ‘org-babel-load-file’ triggers the built-in Org version clashing
>    the newer Org version attempt to be loaded later.
> 
>    It is recommended to move the Org loading code before the
>    ‘org-babel-load-file’ call.

??? I don't use org-babel, I don't load Emacs with a literate Org config file.


> 2. New Org version is loaded manually by setting ‘load-path’, but some
>    other package depending on Org is loaded before the ‘load-path’ is
>    configured.
>    This "other package" is triggering built-in Org version, again
>    causing the version mismatch.
> 
>    It is recommended to set ‘load-path’ as early in the config as
>    possible.

I only use the built-in version or Org, and I'm not sure why that matters since I'm trying to build from the source code.

> 3. New Org version is loaded using straight.el package manager and
>    other package depending on Org is loaded before straight triggers
>    loading of the newer Org version.
> 
>    It is recommended to put
> 
>     (straight-use-package 'org)
> 
>    early in the config.  Ideally, right after the straight.el
>    bootstrap.  Moving ‘use-package’ :straight declaration may not be
>    sufficient if the corresponding ‘use-package’ statement is
>    deferring the loading.

I only use the built-in version or Org, and I'm not sure why that matters since I'm trying to build from the source code.

Any idea what is happening here?

-- 
Jean-Christophe Helary @jchelary@emacs.ch
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/




             reply	other threads:[~2023-05-05  1:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  1:47 l@tlo [this message]
2023-05-05  4:37 ` "Org version mismatch." when building emacs Michael Heerdegen
2023-05-05  5:07 ` Eli Zaretskii
2023-05-05  8:28   ` l@tlo
2023-05-05 10:41     ` Eli Zaretskii
2023-05-05 10:59       ` l@tlo

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=C74BDDA2-777C-4420-B85C-1274CEB88E41@traduction-libre.org \
    --to=lists@traduction-libre.org \
    --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).