On Tue, Jan 08, 2008 at 21:22:09 +0600, Ivan Shmakov wrote: > >>>>> Ivan Shmakov <[EMAIL PROTECTED]> writes: > >>>>> Tino Keitel <[EMAIL PROTECTED]> writes: > > >> it will be nice if KBUILD_OUTPUT is supported. That way, one source > >> tree can be used to build kernels for differend computers with > >> different machines without a clean and messing around with config > >> files. > > > Well, I probably may say that I've some ``initial success'' with > > building in a separate directory. I'd like to mention a couple of > > issues that I've stumbled upon: > > 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: - 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 - make prepare - backup from scripts/kconfig: - zconf.hash.c - zconf.tab.c - lex.zconf.c - make mrproper - restore the above files in scripts/kconfig - go to /where/is/linux-2.6.X.Y-build - copy to build from the source tree: - Documentation - create in build dir (otherwise make-kpkg complains that this is not a kernel source directory): - drivers kernel fs include/linux dev kern fs i386/include - make-kpkg linux-image Regards, Tino -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
