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: Thu, 24 Nov 2022 12:19:31 +0200 [thread overview]
Message-ID: <83zgcgwt70.fsf@gnu.org> (raw)
In-Reply-To: <87a64ghgwy.fsf@posteo.net> (message from Thierry Volpiatto on Thu, 24 Nov 2022 08:49:51 +0000)
> From: Thierry Volpiatto <thievol@posteo.net>
> Cc: 59532@debbugs.gnu.org
> Date: Thu, 24 Nov 2022 08:49:51 +0000
>
> >> NOTE: The only way I found to install tree-sitter was cloning from
> >> github and run make && make install.
> >
> > When you do that, where are libtree-sitter.so and libtree-sitter.so.0
> > installed? in which directory on your system? Is that directory the same as
> > the one where you have the other shared libraries used by Emacs, like the
> > image libraries or GnuTLS?
>
> No, these files are installed in /usr/local/lib.
Then I think you need to tweak tree-sitter's Makefile, or use "make install
PREFIX=/SOME/DIRECTORY", to install the shared libraries and header files
where the rest of them are installed on your system. In any case, so that
the shared libraries end up in a directory that the dynamic linker scans for
shared libraries on your system.
next prev parent reply other threads:[~2022-11-24 10:19 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 [this message]
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
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=83zgcgwt70.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).