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

Add support for build hosts with custom-built kernels, e.g. WSL2 #6

Open
timblaktu opened this issue Aug 13, 2024 · 6 comments · May be fixed by #7
Open

Add support for build hosts with custom-built kernels, e.g. WSL2 #6

timblaktu opened this issue Aug 13, 2024 · 6 comments · May be fixed by #7
Assignees

Comments

@timblaktu
Copy link

Building and running the 22.04 dev container from the variscite container project failed to find my kernel headers:

E: Unable to locate package linux-headers-5.15.153.1-microsoft-standard-WSL2
E: Couldn't find any package by glob 'linux-headers-5.15.153.1-microsoft-standard-WSL2'

I had built and installed a custom WSL kernel from source (to upgrade to 6.x and to add support for automatically mounting usb mass storage devices), so there is no Ubuntu package.

In my fork I intend to modify the scripts here to check for locally-available kernel headers before installing them with apt.

My "build host" is an Ubuntu 22.04.4 LTS VM with 5.15.153.1-microsoft-standard-WSL2 kernel in wsl2 on win11 on x86_64 thinkpad.

@nsdrude
Copy link
Collaborator

nsdrude commented Aug 13, 2024

Which Variscite release are you trying to build with the container?

@nsdrude nsdrude self-assigned this Aug 13, 2024
@timblaktu
Copy link
Author

@nsdrude what exactly do you mean by "Variscite release"?

I originally reproduced this error from master branch of this repo, and have since forked and branched off master to work on a fix. Just getting back to this now..

@timblaktu
Copy link
Author

It appears the error in the OP was caused by my no installing modules along with headers when I installed my locally-build WSL kernel. So, there's no code to fix here, but I'll still submit a PR with minor change in the README to raise awareness about this use case and provide a little reminder.

@timblaktu
Copy link
Author

#7

@nsdrude
Copy link
Collaborator

nsdrude commented Aug 15, 2024

@nsdrude what exactly do you mean by "Variscite release"?

@timblaktu Which Variscite SOM are you using, and which Variscite software release are you trying to build using the docker container?

After clicking on one of our SOMs here, you are presented with all the available software releases: https://variwiki.com/

@timblaktu
Copy link
Author

timblaktu commented Aug 15, 2024

SOM: VAR-SOM-MX8M-PLUS V1.2

Re: SW release, I have used HEAD of mickledore branch as well as refs/tags/mx8mp-yocto-mickledore-6.1.36_2.1.0-v1.2.

I will file another issue for discussing the build problem I'm having now, since this issue is essentially about a documentation change. (I tagged you on the PR, BTW.)

EDIT: Here is the new issue for the docker build layer error: #8

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