On Thursday 12 May 2005 05:27, Sean Dague wrote: > Why do you think we need real module-init-tools on i386? I tested busybox > modprobe loader yesterday, and it worked.
This was intended to remove the need to alter the module tools on the build host. The kernel build happens before the build of the busybox modprobe, with the result that the kernel build tries to use depmod from the build host instead of the one that goes with the kernel being bootstrapped. Your build worked yesterday because you've already got module-init-tools installed on your build host, and you're using it to install the kernel. Ditto the above for mkcramfs, which is built as part of module-init-tools. ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
