Check libseccomp is available at correct version on build #367
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.
This adds a simple build.rs to the seccomp sub-crate. This gives more information in the case of #366, but doesn't necessarily resolve the issue. What this does is it checks to see if
libeseccomp
is available at the correct version. On systems where libseccomp isn't available or is available in an older version the current output is a giant linker error that isn't very helpful. With this change the build will fail right away if the dependency isn't available at an appropriate version and provide much better output.On my system where the libseccomp version is too old it produces this much nicer message: