7e1938d0c3
Now when we have libbpf packaged we want it to be used to build bcc, instead of libbpf Github repo, which is downloaded during the build. The bcc still produces libbcc.so/libbcc.a with libbpf code inside, so nothing changes there.. apart from that they are built from libbpf package now instead of libbpf Github repo The addition is libbcc-no-libbpf.so library, which will be used in applications like bpftrace which needs to link libbpf.so by itself for other features. Signed-off-by: Jiri Olsa <jolsa@redhat.com>
4 lines
545 B
Plaintext
4 lines
545 B
Plaintext
SHA512 (bcc-0.11.0.tar.gz) = 7d6ae598c6ed79eb8ad2d9607f4d20632e7c0d229f1fd33f0503f4e9a1af3db9b63697a1b8e0d1f3d82b0bbe3050bdc09e27dca9106b4527e6844b2b4189a693
|
|
SHA512 (0001-Add-libbcc-no-libbpf.so-library.patch) = 5ac372edeb790c28cbee7067998f238573b3525d85366f941b2c9aa12885c13154d5d3f0af3657b0fc9c54ee7dd64d62a14f8869860bcd8c1005d1b5338a48e2
|
|
SHA512 (0002-Use-libbpf-static-instead-of-libbpf-debugsource-for-.patch) = 8924d39e3b5ef691bbb11e2146097f1b3e68dfe8a2c7116dd6f4d7782861b7758e54843a99576f0821382173b6e3f726e98dab0920ab4726e3bc2abf901553a9
|