From: Eli Zaretskii <eliz@gnu.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 55109@debbugs.gnu.org
Subject: bug#55109: Emacs build fails: Symbol’s function definition is void: byte-compile-set-symbol-position
Date: Mon, 25 Apr 2022 16:27:43 +0300 [thread overview]
Message-ID: <83pml5mgxc.fsf@gnu.org> (raw)
In-Reply-To: <20220425131938.GC2309@cventin.lip.ens-lyon.fr> (message from Vincent Lefevre on Mon, 25 Apr 2022 15:19:38 +0200)
> Date: Mon, 25 Apr 2022 15:19:38 +0200
> From: Vincent Lefevre <vincent@vinc17.net>
> Cc: 55109@debbugs.gnu.org
>
> On 2022-04-25 15:59:15 +0300, Eli Zaretskii wrote:
> > If this was not a freshly cloned repository, did you try "make
> > bootstrap"?
>
> Indeed, this solves the issue. Shouldn't this be detected
> automatically via dependency tracking?
We don't really have any dependency tracking for Emacs Lisp files. It
would be a great addition, if someone develops that, I think, because
such problems are quite frequent during active development.
> (I usually do a "make distclean" first, but I think I forgot.
> Not sure whether this is related here.)
"make distclean" is not enough, AFAIR, because it doesn't delete *.elc
files (again AFAIR). You really need to remove all the *.elc files in
such cases, because the problem is with stale macros that are expanded
into the *.elc files.
next prev parent reply other threads:[~2022-04-25 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 12:54 bug#55109: Emacs build fails: Symbol’s function definition is void: byte-compile-set-symbol-position Vincent Lefevre
2022-04-25 12:59 ` Eli Zaretskii
2022-04-25 13:19 ` Vincent Lefevre
2022-04-25 13:27 ` Eli Zaretskii [this message]
2022-04-25 13:40 ` Lars Ingebrigtsen
2022-04-25 13:52 ` Vincent Lefevre
2022-04-25 14:32 ` Lars Ingebrigtsen
2022-04-25 14:50 ` Vincent Lefevre
2022-04-25 13:00 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pml5mgxc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55109@debbugs.gnu.org \
--cc=vincent@vinc17.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.