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

doc: update eBPF/compilation instructions v4 #10788

Closed

Conversation

lukashino
Copy link
Contributor

Follow-up of #10614

Link to Redmine tickets:

Describe changes:
v4

  • inlined and shortened PATH variable edits in the Rust section
  • can be cloned - be added

v3

  • updates to the docs per Jeff's suggestions
  • removed the instruction to install i386 headers for the eBPF

v2

  • remove recommended configure parameters

v1

  • small edit in eBPF instructions to prefer libbpf-dev package to the cloning&compilation
  • porting changes from the improved version of installation instructions that got merged into master-6.0.x

Copy link

codecov bot commented Apr 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.70%. Comparing base (b224209) to head (879e929).

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     
Flag Coverage Δ
fuzzcorpus 64.16% <ø> (+0.13%) ⬆️
suricata-verify 61.99% <ø> (+<0.01%) ⬆️
unittests 62.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Copy link
Contributor

@jufajardini jufajardini left a 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. :)

Copy link
Member

@victorjulien victorjulien left a 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 \
Copy link
Member

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)

Copy link
Member

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

Copy link
Member

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)

@lukashino
Copy link
Contributor Author

Continues in #10840

@lukashino lukashino closed this Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants