Bug 1961193 - Build bcc from sources without libbpf
Summary: Build bcc from sources without libbpf
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: bcc
Version: 8.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: ---
Assignee: Jerome Marchand
QA Contact: Ziqian SUN (Zamir)
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-17 13:18 UTC by Jerome Marchand
Modified: 2021-11-09 22:36 UTC (History)
5 users (show)

Fixed In Version: bcc-0.19.0-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-09 18:13:24 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4205 0 None None None 2021-11-09 18:13:35 UTC

Description Jerome Marchand 2021-05-17 13:18:29 UTC
Description of problem:
libbpf is included as a submodule in bcc tree and we used to build bcc with that version of libbpf. Because of a github bug, we couldn't build bcc from the standard tarball since the submodule wasn't included. Because of that, we build bcc from a specially packaged archive: bcc-src-with-submodule.tar.gz

We now link bcc to an external libbpf package, so it should be possible to build bcc from the standard source. The issue with bcc-src-with-submodule.tar.gz, is that the archive name doesn't contains the version number, hence never change between versions. rpmdiff now complains about changing content of a source file whose name remained unchanged:
"Upstream source file bcc-src-with-submodule.tar.gz changed content!"

Comment 13 errata-xmlrpc 2021-11-09 18:13:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (bcc bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.