From 727dfcd7eea2520f8e74039f9904a4353fbb3f59 Mon Sep 17 00:00:00 2001 From: Michal Rostecki Date: Tue, 15 Jul 2025 17:22:51 +0200 Subject: [PATCH] ci: Fix bpf-linker installation (#1295) We've recently added an xtask to bpf-linker (aya-rs/bpf-linker#282), which resulted in multiple binary targets. Therefore, bpf-linker has to be installed with the following command: ``` cargo install --git https://github.com/aya-rs/bpf-linker.git bpf-linker ``` The last argument (`bpf-linker`) specifies the binary target. --- .github/workflows/ci.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 6c33086d..b785a768 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -170,7 +170,7 @@ jobs: - uses: Swatinem/rust-cache@v2 - - run: cargo install --git https://github.com/aya-rs/bpf-linker.git + - run: cargo install --git https://github.com/aya-rs/bpf-linker.git bpf-linker - uses: taiki-e/install-action@cargo-hack @@ -297,7 +297,7 @@ jobs: # --force so that bpf-linker gets always relinked against the latest LLVM downloaded above. # # Do this on all system (not just macOS) to avoid relying on rustc-provided libLLVM.so. - - run: cargo install --git https://github.com/aya-rs/bpf-linker.git --no-default-features --force + - run: cargo install --git https://github.com/aya-rs/bpf-linker.git bpf-linker --no-default-features --force - uses: actions/cache@v4 with: