From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Yuan Fu <casouri@gmail.com>, 60415@debbugs.gnu.org
Subject: bug#60415: Emacs master doesn't build if !HAVE_TREE_SITTER
Date: Sun, 01 Jan 2023 09:09:26 +0800 [thread overview]
Message-ID: <87pmbzjc1l.fsf@yahoo.com> (raw)
In-Reply-To: <7d457380-7426-a33e-ee15-c5f9a7e21cce@cs.ucla.edu> (Paul Eggert's message of "Thu, 29 Dec 2022 20:46:32 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On my platform the current Emacs master (commit
> 91ae9f3d12885373d38c3e8d693f7dc210f9d471) won't build, failing with:
>
> ELC progmodes/typescript-ts-mode.elc
>
> In toplevel form:
> progmodes/typescript-ts-mode.el:31:2: Error: Symbol’s function
> definition is vo\
> id: treesit-query-compile
>
>
> Full log (compressed) attached, built from Git on Fedora 37
> x86-64. The best fix isn't immediately obvious to me; adding a
> declare-function doesn't work.
>
> This platform doesn't have the tree-sitter library, so
> HAVE_TREE_SITTER is not defined which means C doesn't define
> treesit-query-compile.
>
> I will probably just install the tree-sitter library to work around
> the bug, but thought I'd document it. Presumably you can simulate it
> by configuring --without-tree-sitter.
Copying in Yuan Fu.
Would people please test their changes on an Emacs *WITHOUT* tree-sitter
before installing them in the future?
next prev parent reply other threads:[~2023-01-01 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 4:46 bug#60415: Emacs master doesn't build if !HAVE_TREE_SITTER Paul Eggert
2023-01-01 1:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-01-01 2:18 ` Yuan Fu
2023-09-06 7:02 ` Stefan Kangas
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=87pmbzjc1l.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=60415@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=luangruo@yahoo.com \
/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).