From: Eli Zaretskii <eliz@gnu.org>
To: "l@tlo" <lists@traduction-libre.org>
Cc: emacs-devel@gnu.org
Subject: Re: "Org version mismatch." when building emacs
Date: Fri, 05 May 2023 13:41:05 +0300 [thread overview]
Message-ID: <83sfcbhxha.fsf@gnu.org> (raw)
In-Reply-To: <1A46463B-630F-463D-93B6-726DDE87DF02@traduction-libre.org> (lists@traduction-libre.org)
> From: "l@tlo" <lists@traduction-libre.org>
> Date: Fri, 5 May 2023 17:28:38 +0900
> Cc: emacs-devel@gnu.org
>
> >> 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
> >
> > Delete all the *.elc files in lisp/org/ and try again.
>
> It looks like it works.
>
> Is there a reason not to indicate that as a possible fix for the issue?
Yes, because we fixed that in a different way. It should not happen
again on the master branch.
> >> Any idea what is happening here?
> >
> > You have stale *.elc files in the tree which still have the old
> > expansion of the macros that were recently changed.
>
> Why doesn't the build process get rid of such files?
Because Make is not aware of Lisp macros and their expansions, and we
don't know how to teach it about them.
next prev parent reply other threads:[~2023-05-05 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 1:47 "Org version mismatch." when building emacs l@tlo
2023-05-05 4:37 ` Michael Heerdegen
2023-05-05 5:07 ` Eli Zaretskii
2023-05-05 8:28 ` l@tlo
2023-05-05 10:41 ` Eli Zaretskii [this message]
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=83sfcbhxha.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lists@traduction-libre.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).