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.

Sign up for GitHub

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

Jump to bottom

Version of libseccomp detection #938

Closed
mYmNeo opened this issue Jul 11, 2016 · 2 comments
Closed

Version of libseccomp detection #938

mYmNeo opened this issue Jul 11, 2016 · 2 comments

Comments

@mYmNeo
Copy link

mYmNeo commented Jul 11, 2016 •
edited

There are three variables called verMajor, verMinor, verMicro to identify the version of libseccomp library, but they are fixed after building.If we upgrading the libseccomp library, the binary can not detect the new version.Should we change the detection fix mode to runtime mode such as using pkg --modversion libseccomp
@cyphar
Copy link
Member

cyphar commented Jul 18, 2016

This is a question for the actual libseccomp-golang project (https://github.com/seccomp/libseccomp-golang). But yes, I'm not entirely sure why they implemented it that way.

@mYmNeo mYmNeo mentioned this issue Jul 18, 2016
Closed
@hqhq
Copy link
Contributor

hqhq commented Oct 31, 2016

This is not a runc issue, traced by seccomp/libseccomp-golang#11 .

@hqhq hqhq closed this as completed Oct 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mYmNeo @cyphar @hqhq