-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
doc: update eBPF/compilation instructions v4 #10788
doc: update eBPF/compilation instructions v4 #10788
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #10788 +/- ##
==========================================
+ Coverage 82.66% 82.70% +0.04%
==========================================
Files 926 926
Lines 247662 247662
==========================================
+ Hits 204722 204834 +112
+ Misses 42940 42828 -112
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Thanks for adding the changes per version, made it easier to know what to look at, too. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some deps feedback. Not all new to this PR, but lets fix it anyway.
pkg-config python3 python3-dev python3-yaml sudo zlib1g \ | ||
zlib1g-dev | ||
cargo install --force cbindgen | ||
sudo apt-get install autoconf automake build-essential cargo cbindgen \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are many things in this list that are not needed by a regular install:
- gosu (no idea why this is here)
- ccache (developer only thing)
- jq (not a build dep)
- m4/libtool (only for developers / working with git)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gosu
seems to also be installed in a few workflow files, w/o actually being used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have CI checks that exactly use these recommendations? I guess we could reverse the logic, and include the CI check commands here using literalinclude
(see app-layer-frames.rst for an example)
Continues in #10840 |
Follow-up of #10614
Link to Redmine tickets:
Describe changes:
v4
v3
v2
v1