Hi Folks at 11.10.2012 16:32, Andrew wrote: > modules.dep is re-generated at kmodules package in main branch; in 4.x > branch it seems that depmod isn't called at all. > Why you don't want to use module auto-probing which should load modules > that are specified in /etc/modules? Or this is remote box that will be > unavailable w/o ipsec.ko?
Reading makefiles is tedious, after all they are meant to be interpreted by machines, not human beings. depmod is done at modules_install in the kernel makefile. The easiest way to regenerate the file is to re-run depmod once the ipsec.ko module is copied to the STAGINg area. Now doing this, the full tree names of the modules are written to the modules.dep file instead of the flat hierarchy used in 4.x. Somewhere this must be stripped. Now what puzzles me is that the build destination for most stuff is not the staging area but the build directory. It appears also that depmod is run against the modules in build and not against the modules in staging. Could someone enlighten me about the reasoning for the two different areas? Thanks Erich
smime.p7s
Description: S/MIME Kryptografische Unterschrift
------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel