Nathan Ridge
Nathan Ridge
Reopening per previous comment
Adding `--force` does seem to result in a usable clang binary.
And subsequent runs of `elfshaker extract` are successful without `--force`.
> If I take the message at face value, it suggests that `link.sh` was modified since you last extracted. Is it possible it was opened in a text editor for...
This does not directly address your request, but are you aware of https://clang.llvm.org/docs/ThreadSafetyAnalysis.html ?
There's some previous discussion of this at https://github.com/clangd/clangd/discussions/1904
To diagnose issues with `--query-driver`, search for "System include extraction" in the log. In this case, we have: > V[09:34:19.989] System include extraction: not allowed driver /toolchain/bin/sh4a_nofpueb-elf-g++ This means clangd...
> Update: Seems like clangd.serverCompletionRanking was set to true and it was causing the issues. At least from what I can notice. Could someone confirm if this is supposed to...
> For example, maybe a setting that puts the `.cache` directory next to the `compile-commands.json` file could be great. As far as I'm aware, that's where clangd puts `.cache` today....
Maybe clangd's `--path-mappings` command-line parameter is suitable for this purpose?