3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-28 12:34:26 +01:00
Code Issues Releases Wiki Activity

readme: multiple versions of packages dont work with SRCDIR

Browse Source
This commit is contained in:
Ciro Santilli
2018-05-20 09:09:33 +01:00
parent faaa791c9f
commit 260155096d
1 changed files with 20 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
README.adoc
View File

@@ -5248,6 +5248,26 @@ and now you can see that a new version of `kernel_module` was built and put insi
ls out/x86_64/buildroot/build/kernel_module-mybranch ls out/x86_64/buildroot/build/kernel_module-mybranch
.... ....
TODO: is there a way to do it nicely for `*_OVERRIDE_SRCDIR` packages from link:buildroot_override[]? I tried:
....
./build -l LINUX_VERSION=mybranch
....
but it fails with:
....
linux/linux.mk:492: *** LINUX_SITE cannot be empty when LINUX_SOURCE is not. Stop.
....
and theI tried:
....
./build -l LINUX_VERSION=mybranch LINUX_SITE="$(pwd)/linux"
....
but it feels hack-ish, and the build was slower than normal, looks like the build was single threaded?
=== BR2_TARGET_ROOTFS_EXT2_SIZE === BR2_TARGET_ROOTFS_EXT2_SIZE
When adding new large package to the Buildroot root filesystem, it may fail with the message: When adding new large package to the Buildroot root filesystem, it may fail with the message: