-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
feat: user precompiled libpcap #25769
Conversation
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.
changes LGTM thanks for making it.
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
CI still complains about the |
I am not sure what this is about
|
How was libpcap made available in the docker image? The compiler can't find the header files. We either need to adapt the include path, or we are missing some files. |
@kuisathaverat I submitted a PR against your branch here: kuisathaverat#7 It seems there is a blank line in the packages block |
fix: remove empty line
/test |
1 similar comment
/test |
/test |
2 similar comments
/test |
/test |
* feat: user precompiled libpcap * Update packetbeat/scripts/mage/pcap.go * fix: remove empty line Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit 4790420)
* feat: user precompiled libpcap * Update packetbeat/scripts/mage/pcap.go * fix: remove empty line Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit 4790420)
* feat: user precompiled libpcap * Update packetbeat/scripts/mage/pcap.go * fix: remove empty line Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com> (cherry picked from commit 4790420) Co-authored-by: Ivan Fernandez Calvo <kuisathaverat@users.noreply.github.com>
What does this PR do?
This PR removes the code related to cross-compile Libpcap before to cross-compile Packetbeat, the library is already compiled in the cross-build Docker image after we merge elastic/golang-crossbuild#91
Why is it important?
This reduces the time to build Packetbeat packages and make the process more robust due to does not have to download third-party resources.
Checklist
- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Relates elastic/golang-crossbuild#63
Requires elastic/golang-crossbuild#91