tree-sitter: Failed to execute C compiler, No such file or directory

[cattokomo]

Hello, It's my first time using tree-sitter. I tried creating grammar by following this tree-sitter page. But failed in step parsing a file.

The error of it:

Failed to load language in current directory

Caused by:
    0: Failed to execute C compiler
    1: No such file or directory (os error 2)

GCC and Clang version:

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go,d,jit --enable-offload-targets=nvptx-none,amdgcn-amdhsa, --enable-offload-defaulted --without-cuda-driver --enable-host-shared --enable-checking=release --disable-werror --with-gxx-include-dir=/usr/include/c++/12 --enable-ssp --disable-libssp --disable-libvtv --enable-cet=auto --disable-libcc1 --enable-plugin --with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir=/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-libphobos --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-12 --without-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --with-build-config=bootstrap-lto-lean --enable-link-mutex --build=x86_64-suse-linux --host=x86_64-suse-linux
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.1 20230124 [revision 193f7e62815b4089dfaed4c2bd34fd4f10209e27] (SUSE Linux)

clang version 15.0.7
Target: x86_64-suse-linux
Thread model: posix
InstalledDir: /usr/bin

Directory list:

binding.gyp  bindings  Cargo.toml  example-file  grammar.js  LICENSE  node_modules  package.json  pnpm-lock.yaml  README.md  src

Step I do:

• gh repo create
• cd tree-sitter-arturo
• pnpm i nan && pnpm i tree-sitter-cli -D
• nvim grammar.js
• pnpm exec tree-sitter generate
• echo hello > example-file
• pnpm exec tree-sitter parse example-file This where the error begins

[ahlinc]

I suspect you don't have an installed compiler..., sorry, I overlooked the output.

Could you describe more your environment? Do you have a repo for a grammar that you tried to build?

Could you try to adapt to your grammar compiler calls that mentioned in a bellow message?

[sogaiu]

The original post seemed to suggest that gcc and clang are available -- may be I misread that -- or perhaps they are not available on PATH?

FWIW, when I had build issues before I modified code near:

tree-sitter/cli/loader/src/lib.rs

Line 427 in c51896d

.with_context(|| "Failed to execute C compiler")?;

to get a dump of the actual compilation command that is executed by the tree-sitter cli. That allowed me to manually perform the invocation and experiment / diganose more easily.

May be it's worth having a debug flag to echo the invocation for investigative purposes?

[ahlinc]

@sogaiu in a temporary tree-sitter fork discussed in a Discord I've added a TREE_SITTER_VERBOSE env variable that outputs actual compilation commands.
It can be set like:

export TREE_SITTER_VERBOSE=1

And get an output by:

tree-sitter generate --build

[sogaiu]

@ahlinc Nice!

Gave it a try:

$ cd ~/src/tree-sitter-clojure
$ TREE_SITTER_VERBOSE=1 TREE_SITTER_DIR=$(pwd)/.tree-sitter tree-sitter.ahlinc generate --build --no-bindings --abi 13
cc -O2 -ffunction-sections -fdata-sections -fPIC -m64 -I /home/user/src/tree-sitter-clojure/src -Wall -Wextra -fno-exceptions -o /home/user/src/tree-sitter-clojure/src/parser.o -c /home/user/src/tree-sitter-clojure/src/parser.c '-DTREE_SITTER_INTERNAL_BUILD=1'
cc -O2 -ffunction-sections -fdata-sections -fPIC -m64 -shared -Wall -Wextra -fno-exceptions -o /home/user/.cache/tree-sitter/lib/clojure.so /home/user/src/tree-sitter-clojure/src/parser.o

I especially like the -o part so I can see the path of the resulting shared object / dynamic library.

Thanks!

[ahlinc]

As you can see in the output the -o parameters are present on every compiler call, it's needed to make a separate unit compilation per file (original tree-sitter compiles all files as a one unit), this is a first step to solve existing compiling issues when for ex. a c++ scanner code requires custom compiling flags or when scanner would be consist from several files, etc.

[sogaiu]

Yes, I get that -o is often present in compiler invocations -- as I understand it though, one does not always get a full path. It depends on the how the invocation is constructed.

Was just happy to be able to see exactly where the shared library ended up because in the past I had encountered issues where the shared library being used was not the one I thought (because of the change in the location that gets referenced ~/.tree-sitter/bin/ vs ~/.cache/tree-sitter/lib).

In any case, thanks again for this :)