From: Eli Zaretskii <eliz@gnu.org>
To: John <jpff@codemist.co.uk>
Cc: 61155-done@debbugs.gnu.org
Subject: bug#61155: 29.0.60; build failures tree sitter
Date: Mon, 30 Jan 2023 14:36:37 +0200 [thread overview]
Message-ID: <83pmaw5hd6.fsf@gnu.org> (raw)
In-Reply-To: <7581-Sun29Jan2023210007+0000-jpff@codemist.co.uk> (message from John on Sun, 29 Jan 2023 21:00:07 +0000)
> Date: Sun, 29 Jan 2023 21:00:07 +0000
> From: John <jpff@codemist.co.uk>
>
>
> For the last couple of days I have been unable to build emacs-29
> branch; error messages are
>
> In toplevel form:
> cedet/semantic/wisent/python.el:30:2: Error: Symbol’s function definition is void: treesit-parser-list
> make[3]: *** [Makefile:332: cedet/semantic/wisent/python.elc] Error 1"
> make[3]: Leaving directory '/home/jpff/GNU/emacs/lisp'
> make[2]: *** [Makefile:366: compile-main] Error 2
> make[2]: Leaving directory '/home/jpff/GNU/emacs/lisp'
> make[1]: *** [Makefile:533: lisp] Error 2
> make[1]: Leaving directory '/home/jpff/GNU/emacs'
> make[1]: Entering directory '/home/jpff/GNU/emacs'
Sorry, should be fixed now.
> I do not have any tree-sitter code. "make bootstrap" appears to work
> but every day it takes too much time. I read tat tree-sitter as not
> necessary but this seems to contradict
As long as "make bootstrap" fixes the build, everything is okay, and
what you see is just an inevitable result of development when some
"hot" features that are optional see a lot of changes. We try to
minimize these problems, but we don't always succeed.
However, this one was a real problem which bootstrap is unable to
fix. It should be fixed now.
next prev parent reply other threads:[~2023-01-30 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 21:00 bug#61155: 29.0.60; build failures tree sitter John
2023-01-30 9:36 ` Robert Pluim
2023-01-30 11:10 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 11:40 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 13:17 ` Eli Zaretskii
2023-01-30 13:22 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 14:20 ` Eli Zaretskii
2023-01-30 14:32 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 14:42 ` Robert Pluim
2023-01-30 15:00 ` Eli Zaretskii
2023-01-30 12:36 ` Eli Zaretskii [this message]
2023-01-30 13:24 ` Robert Pluim
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=83pmaw5hd6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61155-done@debbugs.gnu.org \
--cc=jpff@codemist.co.uk \
/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).