lukash
commented
1 week ago Turns out the clangd wrapper script:
$ cat /nix/store/0vwmhvjdkli5jz8aygdb6psn9nar660h-clang-tools-18.1.8/bin/clangd
#!/nix/store/1xhds5s320nfp2022yjah1h7dpv8qqns-bash-5.2p32/bin/sh
buildcpath() {
local path after
while (( $# )); do
case $1 in
-isystem)
shift
path=$path${path:+':'}$1
;;
-idirafter)
shift
after=$after${after:+':'}$1
;;
esac
shift
done
echo $path${after:+':'}$after
}
export CPATH=${CPATH}${CPATH:+':'}$(buildcpath ${NIX_CFLAGS_COMPILE} \
$(</nix/store/qg9s4a1473skkrsrh1nykfvxm6w5p23d-clang-wrapper-18.1.8/nix-support/libc-cflags)):/nix/store/qg9s4a1473skkrsrh1nykfvxm6w5p23d-clang-wrapper-18.1.8/resource-root/include
export CPLUS_INCLUDE_PATH=${CPLUS_INCLUDE_PATH}${CPLUS_INCLUDE_PATH:+':'}$(buildcpath ${NIX_CFLAGS_COMPILE} \
$(</nix/store/qg9s4a1473skkrsrh1nykfvxm6w5p23d-clang-wrapper-18.1.8/nix-support/libcxx-cxxflags) \
$(</nix/store/qg9s4a1473skkrsrh1nykfvxm6w5p23d-clang-wrapper-18.1.8/nix-support/libc-cflags)):/nix/store/qg9s4a1473skkrsrh1nykfvxm6w5p23d-clang-wrapper-18.1.8/resource-root/include
exec -a "$0" /nix/store/maa8li4ybxv6hb2k23n4akqdk609fh1r-clang-18.1.8/bin/$(basename $0) "$@"Adds include paths to clangd via environmental variables (CPATH and CPLUS_INCLUDE_PATH). These include paths are unwanted for ARM compilation and break clangd, with wrong include paths the language server doesn't work properly.
NickCao
Describe the bug
clangdextracts x86_64 desktop include flags fromarm-none-eabi-gcc, e.g. a python include, QT includes etc.Reported as clangd issue: https://github.com/clangd/clangd/issues/2181
After some discussion there it seems likely there is some weird NixOS interaction causing this.
This is what the
arm-none-eabi-gccprints:Expected behavior
On ARM embedded include flags are extracted by
clangd.Notify maintainers
@Patryk27
Metadata
Add a :+1: reaction to issues you find important.