As I work through getting 3.5.x to build on debian stable, I hit a problem. The main Makefile does a make ... modules_install just after it runs mklibs. Since debian stable is a 2.4.x system, it doesn't have module-init-tools installed, and the Makefile detonates there.
If I install module-init-tools from backport.org, the install succeeds, and then the very next thing that happens is that the make proceedure starts building module-init-tools from the source in the initrd_source tree. So, it looks like there's an ordering problem in the build. That is, if module-init-tools were built from source and used to do modules_install, the build could succeed without having to resort to backport.org. I'm wondering if someone more familiar with that part of the build (Brian?, Dann?) could comment on this. Is fixing it as simple as moving module-init-tools from initrd_source to src and installing it in the boel_binaries tarball prior to the modules_install? ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
