-
Notifications
You must be signed in to change notification settings - Fork 12
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
no-km build options missing #34
Comments
Also, when running a build in a new Ubuntu 22.04 VM, you need to run the pip3 install command as root to ensure that the toml binary is in the path. Otherwise, the build script throws an error. From: pip3 install toml-cli |
Hi @bobdukeCL , The removal of no-km options was intentional. Back when this project was started, we've seen a issue with dkms while installing ti-img-rogue and cryptodev modules. The dkms tried to pick Host's Linux version headers instead of version that's getting installed in the target FS. So we created km and no-km options. KM for building on target itself and -NO-KM for building on Host. Since then, the deb packages were updated a lot and we no longer see this issue. So we unified the configs. The README.md has to be updated to point to the latest build options that are available. Also, Yes sudo is required for installing toml-cli. I'll be updating the README today. PS: If you want a FileSystem without out-of-tree kernel modules, you can always update the bdebstrap configs. |
The README.md mentions:
sudo ./build.sh am62x_bookworm-no-km_09.00.00.006
But the builds.toml file no longer contains no-km build options.
Is this intentional?
The text was updated successfully, but these errors were encountered: