all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Compiling emacs 30.0.50 on Fedora 38 with tree-sitter
@ 2023-06-08 15:02 Frederick Bartlett
  2023-06-09 20:04 ` Emanuel Berg
  0 siblings, 1 reply; 2+ messages in thread
From: Frederick Bartlett @ 2023-06-08 15:02 UTC (permalink / raw)
  To: help-gnu-emacs

This is the first time I’ve ever compiled emacs; I was following Mickey
Petersen’s guide at
https://www.masteringemacs.org/article/how-to-get-started-tree-sitter

Running configure --with-tree-sitter produced an error: the system couldn’t
find the tree-sitter pkgconfig file.

Not quite understanding the problem, I simply copied tree-sitter.pc from
$PKG_CONFIG_PATH/pkgconfig/tree-sitter to $PKG_CONFIG_PATH – and then it
worked.

Was I lucky, or is this what one is expected to do?

Thanks!
Fred


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Compiling emacs 30.0.50 on Fedora 38 with tree-sitter
  2023-06-08 15:02 Compiling emacs 30.0.50 on Fedora 38 with tree-sitter Frederick Bartlett
@ 2023-06-09 20:04 ` Emanuel Berg
  0 siblings, 0 replies; 2+ messages in thread
From: Emanuel Berg @ 2023-06-09 20:04 UTC (permalink / raw)
  To: help-gnu-emacs

Frederick Bartlett wrote:

> This is the first time I’ve ever compiled emacs; I was following Mickey
> Petersen’s guide at
> https://www.masteringemacs.org/article/how-to-get-started-tree-sitter
>
> Running configure --with-tree-sitter produced an error: the system couldn’t
> find the tree-sitter pkgconfig file.
>
> Not quite understanding the problem, I simply copied tree-sitter.pc from
> $PKG_CONFIG_PATH/pkgconfig/tree-sitter to $PKG_CONFIG_PATH – and then it
> worked.
>
> Was I lucky, or is this what one is expected to do?

Well, obviously it is a path error/file organization mismatch
but I wonder, is this the kind of situations that has led to
the strange belief "if you upgrade Emacs you will brake
packages"?

Because if so one, it isn't true, and two, it is even unfair
to the package managers whoever they may be because from their
perspective it's assumed paths are correct.

Speaking even more broadly it is strange that you can't
compile Emacs because of other source that isn't even compiled
in the same process necessarily.

However if we return to reality it isn't a problem since
compiling Emacs don't break anything.

-- 
underground experts united
https://dataswamp.org/~incal




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-06-09 20:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-06-08 15:02 Compiling emacs 30.0.50 on Fedora 38 with tree-sitter Frederick Bartlett
2023-06-09 20:04 ` Emanuel Berg

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.