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

rename libbpf.{a,so} to libbcc_bpf.{a,so} #2290

Merged
merged 1 commit into from
Mar 27, 2019
Merged

rename libbpf.{a,so} to libbcc_bpf.{a,so} #2290

merged 1 commit into from
Mar 27, 2019

Conversation

yonghong-song
Copy link
Collaborator

This is based on discussion in netdev regarding to libbpf repo
packaging:
https://lore.kernel.org/bpf/20190325202009.GA14511@krava/T/#t

The libbpf repo https://github.com/libbpf/libbpf contains
the linux:tools/lib/bpf codes plus some other uapi and auxiliary
headers. It is natural for libbpf repo to generate a
libbpf.{a,so} installable as a package.

To avoid conflicts, let us rename bcc libbpf.{a,so}
to libbcc_bpf.{a,so}.

Signed-off-by: Yonghong Song [email protected]

This is based on discussion in netdev regarding to libbpf repo
packaging:
  https://lore.kernel.org/bpf/20190325202009.GA14511@krava/T/#t

The libbpf repo https://github.com/libbpf/libbpf contains
the linux:tools/lib/bpf codes plus some other uapi and auxiliary
headers. It is natural for libbpf repo to generate a
libbpf.{a,so} installable as a package.

To avoid conflicts, let us rename bcc libbpf.{a,so}
to libbcc_bpf.{a,so}.

Signed-off-by: Yonghong Song <[email protected]>
@yonghong-song
Copy link
Collaborator Author

cc @olsajiri

@yonghong-song yonghong-song merged commit 3677925 into master Mar 27, 2019
palexster pushed a commit to palexster/bcc that referenced this pull request Jul 7, 2019
This is based on discussion in netdev regarding to libbpf repo
packaging:
  https://lore.kernel.org/bpf/20190325202009.GA14511@krava/T/#t

The libbpf repo https://github.com/libbpf/libbpf contains
the linux:tools/lib/bpf codes plus some other uapi and auxiliary
headers. It is natural for libbpf repo to generate a
libbpf.{a,so} installable as a package.

To avoid conflicts, let us rename bcc libbpf.{a,so}
to libbcc_bpf.{a,so}.

Signed-off-by: Yonghong Song <[email protected]>
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.

None yet

2 participants