failure to compile eBPF on RedHat CoreOS 4.9 from sysdig 0.28.0 container
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp, linux
- Domain
- build-system, operating-systems
Research direction
Start with the bpf/Makefile and the kernel build invocation in the log, then compare the dependency and toolchain setup in sysdig 0.28.0 and 0.29.3 with the successful 0.27.1 image on RedHat CoreOS 4.9. Reproduce the compile failure and verify that the eBPF probe builds without the libelf dependency error.
Written by the indexing model from the issue text.
Description
We are unable to compile sysdig eBPF probe on RedHat CoreOS 4.9 from Sysdig 0.28.0 image.
Seems like there is toolchain package missing: libelf-devel.
Have also tried the following images:
sysdig 0.29.3 - same error
sysdig 0.27.1 - successful
Logs:
- Trying to compile the eBPF probe (scap_rhcos_4.18.0-305.30.1.el8_4.x86_64_1.o)
make: Entering directory '/opt/sysdig/src/scap-2160111cd088aea9ae2235d3385ecb0b1ab6623c/bpf'
make -C /lib/modules/4.18.0-305.30.1.el8_4.x86_64/build M=$PWD
make[1]: Entering directory '/host/usr/src/kernels/4.18.0-305.30.1.el8_4.x86_64'
make[1]: Leaving directory '/host/usr/src/kernels/4.18.0-305.30.1.el8_4.x86_64'
Makefile:984: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop.
make: Leaving directory '/opt/sysdig/src/scap-2160111cd088aea9ae2235d3385ecb0b1ab6623c/bpf'
make: *** [Makefile:20: all] Error 2
- Dominant language
- C++
- Stars
- 8.3k
- Forks
- 753
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from draios/sysdig
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
difficulty-easy feature-request pinned
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
feature-request pinned
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·