-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Test for NFT_MSG_MAX
fails on my Linux machine
#1080
Comments
This is expected, the values of constants change across different kernel versions, and libc contains static values of constants. |
This commit removes special cases for sparc64 which caused test failures on a sparc64 system (Debian, glibc 2.28). With these changes, the ABI tests pass except for the known test failure from rust-lang#1080
Adjust for newer glibc on sparc64 This commit removes special cases for sparc64 which caused test failures on a sparc64 system (Debian, glibc 2.28). With these changes, the ABI tests pass except for the known test failure from #1080
Same issue on Ubuntu 18.10 cosmic
|
As mentioned, this is expected behavior, that version of Linux is not supported by libc. The path forward here is to upgrade the version of Linux that libc supports on CI, and then update the constants to match that version. |
Fixed on master. |
Fixed by 4497a78. |
glibc 0.28
Linux 4.18.6.arch1
Arch Linux
NFT_MSG_MAX
, from /usr/include/linux/netfilter/nf_tables.h:It seems like
were added and thus
NFT_MSG_MAX
increased. Linux doesn't consider this a breaking change. I'd assume that more messages might be added in the future, so just adjusting the constant in libc as a breaking change doesn't seem to be useful.The text was updated successfully, but these errors were encountered: