bcc_elf: mkostemp() requires _GNU_SOURCE#1
Open
luisgerhorst wants to merge 1 commit intopyroscope-io:fix/speeedfrom
Open
bcc_elf: mkostemp() requires _GNU_SOURCE#1luisgerhorst wants to merge 1 commit intopyroscope-io:fix/speeedfrom
luisgerhorst wants to merge 1 commit intopyroscope-io:fix/speeedfrom
Conversation
Author
|
On Slack, @korniltsev pointed out that this will be obsolete when grafana/agent#3953 is done (which does not use bcc). Still leaving this here for reference. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As per mkostemps(3), mkostemp() (used in line 842) requires _GNU_SOURCE. Therefore define it before the includes if it not defined by the env/compiler. Otherwise I encounter the following error on my system:
I noticed that this is still not fixed in upstream bcc v0.27. However, updating (and rebasing) the bcc version used by pyroscope caused a buch of other errors on my system. Should I instead upstream the fix and then create a pull request to update the bcc version used by pyroscope?