From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: 59532@debbugs.gnu.org
Subject: bug#59532: 28.2; Unable to build emacs with tree-sitter installed
Date: Sun, 04 Dec 2022 13:44:22 +0200 [thread overview]
Message-ID: <83h6ybbdgp.fsf@gnu.org> (raw)
In-Reply-To: <87lennigzq.fsf@posteo.net> (message from Thierry Volpiatto on Sun, 04 Dec 2022 10:41:00 +0000)
> From: Thierry Volpiatto <thievol@posteo.net>
> Cc: 59532@debbugs.gnu.org
> Date: Sun, 04 Dec 2022 10:41:00 +0000
>
> > It is not wrong, it just assumes a well-configured system, where shared
> > libraries live in a sensible place.
>
> No, if one follow the directions in "* Building Emacs with tree-sitter"
> it will fail, well-configured system or not as long as you consider
> "/usr/local/lib" as a wrong place to install tree-sitter.
/usr/local/lib is not a wrong place. Depending on your system
configuration, it might be right or it might be wrong.
> I just remind you that it is tree-sitter itself with make+make install
> that install tree-sitter libs in this place.
No, that's the tree-sitter's _default_. When you use its Makefile, you are
supposed to review it and change the default as needed.
> I just say that for people trying to install tree-sitter, if it just for
> me I am fine with "--without-tree-sitter".
Those notes are not for everyone, they will be deleted soon. They were
meant to help people who wanted to work on new modes based on tree-sitter.
next prev parent reply other threads:[~2022-12-04 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 6:46 bug#59532: 28.2; Unable to build emacs with tree-sitter installed Thierry Volpiatto
2022-11-24 8:03 ` Eli Zaretskii
2022-11-24 8:49 ` Thierry Volpiatto
2022-11-24 10:19 ` Eli Zaretskii
2022-11-24 10:47 ` Thierry Volpiatto
2022-11-24 10:58 ` Eli Zaretskii
2022-12-04 7:59 ` Thierry Volpiatto
2022-12-04 10:03 ` Eli Zaretskii
2022-12-04 10:41 ` Thierry Volpiatto
2022-12-04 11:44 ` Eli Zaretskii [this message]
2023-01-07 22:45 ` Yuan Fu
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=83h6ybbdgp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59532@debbugs.gnu.org \
--cc=thievol@posteo.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 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).