From: Thierry Volpiatto <thievol@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59532@debbugs.gnu.org
Subject: bug#59532: 28.2; Unable to build emacs with tree-sitter installed
Date: Sun, 04 Dec 2022 07:59:21 +0000 [thread overview]
Message-ID: <87pmczio23.fsf@posteo.net> (raw)
In-Reply-To: <83r0xswre3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Thierry Volpiatto <thievol@posteo.net>
>> Cc: 59532@debbugs.gnu.org
>> Date: Thu, 24 Nov 2022 10:47:08 +0000
>>
>> > 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.
>>
>> Yes, of course I can do that but it seems weird that ./configure locate
>> these files and make doesn't, isn't it?
>
> The configure script doesn't run any programs, it only tries to compile and
> link them. By contrast, the build process does run Emacs, and that requires
> to find the library (if the Lisp code processed by temacs needs to call the
> library).
So the documentation in emacs/admin/notes/tree-sitter/starter-guide is
wrong (* Building Emacs with tree-sitter).
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2022-12-04 7:59 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmczio23.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=59532@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.