On Thu, Jan 10, 2008 at 07:30:32 +0600, Ivan Shmakov wrote: > >>>>> Tino Keitel <[EMAIL PROTECTED]> writes: > > >> I'm currently testing the following hack: It requires one to use > >> kbuild first, e. g.: > > >> $ cd /usr/src/linux-2.6.X.Y > >> $ make O=/where/is/linux-2.6.X.Y-build menuconfig ... > >> $ > > >> Then, make-kpkg(1) could be used: > > >> $ cd /where/is/linux-2.6.X.Y-build $ make-kpkg ... ... > > > Hi, > > > thanks a lot. The patch works in general, but I had to do the > > following to get it working: > > Thanks for the feedback! I hope to return to improving this > change shortly. > > > - cd /usr/src/linux-2.6.X.Y > > - mkdir /where/is/linux-2.6.X.Y-build > > - make O=/where/is/linux-2.6.X.Y-build menuconfig > > Yes, these steps are as intended. > > > - make prepare > > - backup from scripts/kconfig: > > - zconf.hash.c > > - zconf.tab.c > > - lex.zconf.c > > - make mrproper > > - restore the above files in scripts/kconfig > > Could you investigate why the above is necessary?
Because I didn't start with a clean source tree. When I started make-kpkg, it complained that the source directory is not clean and that I should use make mrproper. That mrproper removed the above .c files and then the compilation failed. So when I start with a clean source tree, do the make O=... then I can build the kernel without messing around with these .c files. Sorry for the confusion. So the only things that are left are the creation of the required directories in the build dir and the copy of "Documentation". Now that out-of-tree builds are working, I feel the desire of a per directory kernel-pkg.conf (maybe something like .kernel-pkg.conf). This way, the user can save the settings like revision and initrd in the build directory, so that just a make-kpkg linux-image is sufficient. Regards, Tino -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
