-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Fails to build on arm64 #14031
Comments
is it possible that not systemd changed but libseccomp? old libseccomp used to define __NR_sysctl and friends to negative values on systems that do not support them. The newest libseccomp doesn#t do that anymore. Maybe libseccomp was updated like that on debian at the same time? |
Good call, libseccomp was updated between 243-5 and 243-6: https://tracker.debian.org/news/1079515/accepted-libseccomp-242-1-source-into-unstable/ Seems like 2.4.2-1 does trigger this build failure. |
…namespace invasion A follow-up for 59b6572, adding the same conditioning for all cases of our __NR_xyz use. Fixes: systemd#14031
Can you check if #14032 fixes this for you? |
The above PR does fix the build failure on arm64. |
See systemd/systemd#14031 Gbp-Dch: Short
…namespace invasion A follow-up for 59b6572, adding the same conditioning for all cases of our __NR_xyz use. Fixes: systemd#14031 (cherry picked from commit 4df8fe8)
…namespace invasion A follow-up for 59b6572, adding the same conditioning for all cases of our __NR_xyz use. Fixes: systemd#14031
…namespace invasion A follow-up for 59b6572, adding the same conditioning for all cases of our __NR_xyz use. Fixes: systemd#14031
v243 fails to build on arm64 on Debian sid:
Full build log available at https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=arm64&ver=243-6&stamp=1573744894&raw=0
I'm not entirely sure what changed between 243-5 and 243-6 which could trigger that error.
243-5 built fine https://buildd.debian.org/status/fetch.php?pkg=systemd&arch=arm64&ver=243-6&stamp=1573744894&raw=0
The text was updated successfully, but these errors were encountered: