From: Colin Baxter <m43cap@yandex.com>
To: Yuan Fu <casouri@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Make failure - progmodes/typescript-ts-mode.elc
Date: Fri, 30 Dec 2022 09:42:58 +0000 [thread overview]
Message-ID: <87v8ltmdlp.fsf@yandex.com> (raw)
In-Reply-To: <F41952CF-E35C-4D80-8D0C-D095940FBBCF@gmail.com> (Yuan Fu's message of "Thu, 29 Dec 2022 11:35:43 -0800")
>>>>> Yuan Fu <casouri@gmail.com> writes:
>> On Dec 29, 2022, at 4:26 AM, Colin Baxter <m43cap@yandex.com> wrote:
>>
>>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: Colin Baxter <m43cap@yandex.com> Date: Thu, 29 Dec 2022
>>>> 09:34:36 +0000
>>>>
>>>>
>>>> On a fresh git pull I have this 'make' failure:
>>>>
>>>> --8<---------------cut
>>>> here---------------start------------->8---
>>>>
>>>> ELC progmodes/typescript-ts-mode.elc
>>>>
>>>> In toplevel form: progmodes/typescript-ts-mode.el:31:2: Error:
>>>> Symbol’s function definition is void: treesit-query-compile
>>>> Makefile:332: recipe for target
>>>> 'progmodes/typescript-ts-mode.elc' failed make[4]: ***
>>>> [progmodes/typescript-ts-mode.elc] Error 1 make[4]: Leaving
>>>> directory '/home/redknight/git/emacs/lisp' Makefile:366: recipe
>>>> for target 'compile-main' failed make[3]: *** [compile-main]
>>>> Error 2 make[3]: Leaving directory
>>>> '/home/redknight/git/emacs/lisp' Makefile:533: recipe for
>>>> target 'lisp' failed make[2]: *** [lisp] Error 2 make[2]:
>>>> Leaving directory '/home/redknight/git/emacs' make[2]: Entering
>>>> directory '/home/redknight/git/emacs' *** *** "make all" failed
>>>> with exit status 2. *** *** You could try to: *** - run "make
>>>> bootstrap", which might fix the problem *** - run "make V=1",
>>>> which displays the full commands invoked by make, *** to
>>>> further investigate the problem ***
>>>>
>>>> --8<---------------cut
>>>> here---------------end--------------->8---
>>>>
>>>> I have tried both make bootstrap <RET>, and make extraclean
>>>> <RET> followed by make <RET>, but to no avail.
>>>>
>>>> I am on Linux bluestar 4.9.0-19-686-pae #1 SMP Debian 4.9.320-2
>>>> (2022-06-30) i686 GNU/Linux.
>>
>>> Doesn't happen here. However, I'm guessing that your build is
>>> without tree-sitter. Please make a point of using
>>
>> Yes, I don't compile --with-tree-sitter. I don't have the
>> tree-sitter libraries.
> Sorry about that. I fixed js.el. I’ve setup a without-tree-sitter
> build, so I’ll be able to catch these errors next time.
> Yuan
Thank you, Yuan. The master branch now builds for me successfully.
Best wishes,
Colin Baxter.
prev parent reply other threads:[~2022-12-30 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 9:34 Make failure - progmodes/typescript-ts-mode.elc Colin Baxter
2022-12-29 10:47 ` Eli Zaretskii
2022-12-29 12:26 ` Colin Baxter
2022-12-29 19:35 ` Yuan Fu
2022-12-30 9:42 ` Colin Baxter [this message]
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=87v8ltmdlp.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=casouri@gmail.com \
--cc=eliz@gnu.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).