| commit | d713349effab8e72727478c92ac75723a451ae72 | [log] [tgz] |
|---|---|---|
| author | Ed Tanous <etanous@nvidia.com> | Thu Jul 24 12:20:11 2025 -0700 |
| committer | Ed Tanous <etanous@nvidia.com> | Thu Jul 24 12:22:54 2025 -0700 |
| tree | 5ceaccb27d31c46e5f77de44c2ed933799fb2e63 | |
| parent | e4b761fe0a9c789c2c8a7147081c138ad9e19268 [diff] |
Move clang builds to use lld Clang builds are currently complaining about a missing LLVMGold plugin. ``` /usr/bin/ld: /usr/lib/llvm-20/bin/../lib/LLVMgold.so: error loading plugin: /usr/lib/llvm-20/bin/../lib/LLVMgold.so: cannot open shared object file: No such file or directory ``` In the past this was because the plugin got moved into an llvm-linkers apt package unintentionally. The move to the new ubuntu seems to have forced this to be a problem again, and adding the llvm-linkers package doesn't fix it like it had in the past. While compiling with clang and linking with ld should work fine, it's likely simpler to run the whole llvm toolchain when doing clang builds. Therefore, move meson clang builds to LLD. Change-Id: Ibf952a31695061a958cb437d74ea4b264ce96aaa Signed-off-by: Ed Tanous <etanous@nvidia.com>
Build script for CI jobs in Jenkins.
Formatting linters sometimes change stylistic output across releases. Separately, some linters are not version-pinned in the CI container, as pinning would drive either frequent maintenance with upgrades or stagnation of the code-base against older versions.
The combination may result in inconsistent formatting opinions across CI worker nodes[^1].
If you see such behaviour consider changing the thing to force a container refresh.
[^1]: The collection of container builds across all worker nodes may not hold a consistent set of tool versions despite being built from the same specification: The inconsistencies emerge from the cadence of upstream tool package updates beating against the cadence of container rebuilds on the worker nodes.