On 9/21/19 10:39 PM, DJ Lucas via lfs-dev wrote:
On 9/21/2019 10:02 PM, DJ Lucas via lfs-dev wrote:
On 9/20/2019 11:29 PM, Kevin Buckley via lfs-dev wrote:
On Sat, 21 Sep 2019 at 07:46, DJ Lucas via lfs-dev
<[email protected]> wrote:
In the book, we currently have the text "Install the modules, if the
kernel configuration uses them:" - this is incorrect. All kernels
use them, whether they are built-in or not, and this step is
required to populate /lib/modules/$(uname
-r)/modules.{builtin,dep,order,*}.
I was not entirely correct above.
So, this is not the case for CONFIG_MODULES=n.
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
I guess the existing works, but this is more clear regarding the
configuration: "If you've enabled loadable modules support in the
kernel..." Note that this is different than building without any config
items selected as a module (M).
Seems odd to depend on the overall setting. If loadable modules support
is set, but you don't build any modules, why should the SW care?
I agree that the above would be a little unusual, but the test should
not be whether the kernel is wired for modules, but if the module files
actually exist.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
