Skip to content

Conversation

@kernel-patches-daemon-bpf
Copy link

Pull request for series with
subject: selftests/bpf: propagate LLVM toolchain into runqslower sub-make
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1025135

@kernel-patches-daemon-bpf
Copy link
Author

Upstream branch: d6ec090
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1025135
version: 1

@kernel-patches-daemon-bpf
Copy link
Author

Upstream branch: d6ec090
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1025135
version: 1

@kernel-patches-daemon-bpf
Copy link
Author

Upstream branch: d088da9
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1025135
version: 1

@kernel-patches-daemon-bpf
Copy link
Author

Upstream branch: e0940c6
series: https://patchwork.kernel.org/project/netdevbpf/list/?series=1025135
version: 1

The runqslower build invokes a nested make, but the selected LLVM
toolchain (via LLVM=-<version>) is not propagated. This causes the
sub-make to call the system-default 'clang' and 'llvm-strip' even when
a specific LLVM version is intended.

    # LLVM=-20 V=1 make -C tools/testing/selftests/bpf
    ...
    make -C tools/bpf/runqslower ...
    clang -g -O2 --target=bpfel -I... -c runqslower.bpf.c -o runqslower.bpf.o && \
          llvm-strip -g runqslower.bpf.o
    /bin/sh: 1: clang: not found

    (expected: clang-20 and llvm-strip-20)

Propagate CLANG and LLVM_STRIP to the sub-make to ensure LLVM version
consistency across all builds.

Signed-off-by: Hoyeon Lee <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants