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.

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

kselftests: Add gcc-10-plugin-dev package to Debian containers (only GCC ones) #1041

Closed
musamaanjum opened this issue Feb 16, 2022 · 1 comment
Assignees

Comments

@musamaanjum
Copy link
Contributor

gcc-10-plugin-dev package is needed in Debian userspace for enabling GCC_PLUGIN_STACKLEAK config in the kernel. This config is needed in kernel for tools/testing/selftests/LKDTM/STACKLEAK_ERASING.sh test. At this time if we add gcc-10-plugin-dev package to the Bullseye and enable GCC_PLUGIN_STACKLEAK config. Kernel compilation fails:

/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386.h:2500:10: fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory
 2500 | #include "common/config/i386/i386-cpuinfo.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Looking at this error, I've found out that support for GCC Plugins is broken in Bullseye. There is a bug filed here. The workaround is possible by applying a patch. But I don't think that it is worthwhile. Let's wait for the bug to get fixed in Bullseye or wait for a new stable Debian release with this error fixed and KernelCI starts using that new Debian version. Then gcc-10-plugin-dev package should be added to the build Docker containers of GCC versions like gcc-10_x86 etc.

@musamaanjum musamaanjum changed the title Add gcc-10-plugin-dev package to Debian containers (only GCC ones) kselftests: Add gcc-10-plugin-dev package to Debian containers (only GCC ones) Feb 18, 2022
@musamaanjum musamaanjum self-assigned this Apr 5, 2022
@musamaanjum
Copy link
Contributor Author

After merging #1078 and in-review patch: https://lore.kernel.org/linux-kselftest/20220217205620.2512094-1-usama.anjum@collabora.com/t/#u, this issue is fixed. There is no need to do anything else. I've tested it in the local environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant