-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add support for compiling kernel per distribution #4487
Conversation
/rebase |
🧹 PR Cleanup Quest 🧹 @igorpecovnik The workflow files seem to be vastly different today compared to when this PR was made ~two years ago. Is this issue that this PR solved still a problem today? |
@ColorfulRhino The problem remains relevant. P.S. |
Thanks for your reply! After looking at this more closely, the goal is to e.g. build one kernel for Debian Bookworm, one for Debian Trixie, one for Ubuntu Noble and so on, each with the compiler and defconfig from the respective distribution? If yes, I do agree that this seems pretty complex and especially heavy on building and maintenance. I don't think I'm understanding the issue yet though, like what this would solve. Honestly, so far I never had issues with the normal "non-native" kernel. I like it, since it can be used even for other distros if needed.
I'll leave that up to Igor :) |
It's much more complicated than that. The user uses Ubuntu 20.04 and when updating receives packages collected in Ubuntu 24.04 |
Yes, agree. |
So e.g. if I install a freshly built edge kernel on a board running Ubuntu 20.04, the kernel may try to access library functions which Ubuntu 20.04 doesn't have?
Are there some packages included in the kernel that will be installed when updating the kernel?
I see, this is bad. But the solution seems very complex. Maybe at some point there will magically be an easy solution, one can always hope 😄 |
Description
In order to achieve full compatibility between kernel, headers and libc, we need to build kernel per distribution, native, with distro compilers. In order to achieve that, we also need to store kernel into its repository. This method also significantly increases arm64 build load.
To do:
Jira reference number AR-1407
How Has This Been Tested?
Checklist: