Updated rocm-sources ebuilds that ensures kernel files with executabl… #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e attributes remain (e.g., so "make menuconfig" etc. will work). (These ebuilds make use of the kernel-2 eclass.) Each ebuild exists in its own slot and when the ebuild is removed no files are deleted from /usr/src (i.e., which is the same behaviour of gentoo-sources). To use with other kernels, simply copy the ebuild renaming the file's version and set CKV in the ebuild file to be the actual kernel release of the repository. The latter can be found at the top of the repository's root Makefile. Use Gentoo conventions for formatting such, e.g., 5.9.0_rc2.
|
Hmmm I missed adding |
|
Ok, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses justxi/rocm Issue #186 with ebuilds that will install rocm-sources kernel source code preserving all files' executable attributes (e.g., .sh and .py files) so the kernel can be built.
Each ebuild is in its own SLOT so as to not interfere with other kernels. Additionally when the ebuild is removed, the files in /usr/src are left as-is. The features of the kernel-2 eclass were exploited to allow for the ROCm designation to be part of the EXTRAVERSION part of the installed name with the kernel version itself being part of the base name. For example, if one runs
emerge -av rocm-sources:4.3.1then it will be installed in/usr/src/linux-5.11.0-rocm-4.3.1and will retain the5.11.0-rocm-4.3.1part of the name for built kernel files written to/boot.To make releases for other kernels do the following:
CKV="5.9.0_rc2". (This will cause the emitted name to have the Linux kernel version in it as well as the ebuild version information.)I was able to build kernels for v4.3.0 and v4.3.1 and all appears to be good --except on my system there are no audio devices. (After some web searching, this may well kernel 5.11 issue.) I suspect since I run Gentoo testing
~amd64, I am unable to build the kernels before v4.3.0 due toarch/x86/entry/thunk_64.o: warning: objtool: missing symbol tableand similar errors even using GCC v8. (That said, some time ago I was able to build v4.1.0 --so an update to a tool, e.g., binutils might be triggering this issue. Others may well be able to build these kernels.)