Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove libbcc dependency on llvm headers #5018

Merged
merged 2 commits into from
May 30, 2024

Conversation

chantra
Copy link
Contributor

@chantra chantra commented May 29, 2024

This should fix the issue brought up in #4997 where llvm-devel was made a requirement for libbcc because of the presence of llvm-config.h include in bpf_module.h.

This changes moved the include inside bpf_module.cc so it does not leak outside of a build requirement.

rpm and deb specs were updated, but I was not able to test them.

In iovisor#4737 I added depedency on llvm-config.h in order to discover what LLVM version
is being used. This was only meant to be used at build time.
By adding llvm-config.h in bpf_module.h, a public header of libbcc, I introduced
a dependency on llvm-dev to libbcc which is unnecessary.

This change removes the include from `bpf_module.h`, which should be enough, and
add it to `bpf_module.cc` instead.

Fixes iovisor#4997

Signed-off-by: Manu Bretelle <chantr4@gmail.com>
This is essentially reverting iovisor#4921

Signed-off-by: Manu Bretelle <chantr4@gmail.com>
@yonghong-song yonghong-song merged commit 1d8daaa into iovisor:master May 30, 2024
12 checks passed
@chantra chantra deleted the bcc_llvm_config_h branch May 30, 2024 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants