Hi when I use make-kpkg to make a custom kernel on single processor system there are no problems. Kernel image and headers packages build successfully.

On an amd64 dual core this is what happens
invocation:
cd /usr/src/linux-source-2.6.32
make mrproper
make-kpkg clean (not necessary just in case)
rm -rf debian (not necessary)
make menuconfig

CONCURRENCY_LEVEL=3 make-kpkg --arch=amd64 --append-to-version='custom12' --initrd kernel_image kernel_headers > ~/out 2>~/out-error

normal output:
make[2]: Leaving directory `/usr/src/linux-source-2.6.32'
make[1]: Leaving directory `/usr/src/linux-source-2.6.32'
error code 0
( compile and link were successful)

error output:
[: 9: -f: unexpected operator
WARNING: Couldn't open directory /usr/src/linux-source-2.6.32/debian/linux-image-/lib/modules/2.6.32-22-generic: No such file or directory
FATAL: Could not open /usr/src/linux-source-2.6.32/debian/linux-image-/lib/modules/2.6.32-22-generic/modules.dep.temp for writing: No such file or directory
make[2]: *** [_modinst_post] Error 1
make[1]: *** [debian/stamp/install/linux-image-] Error 2
make: *** [kernel_image] Error 2
( the building of the deb packages has failed)

Notice appendage is 'custom12' but why is there /lib/modules/2.6.32-22-generic there on the FATAL line?
make-kpkg must be doing a `uname -r` because my boot kernel is vmlinuz-2.6.32-22-generic?

Thanks any help would be appreciated?
Rob Key
robkey is online now Report Post Edit/Delete Message

thought you would have to do a
make-kpkg clean before make-kpkg (?)
And I isn't it a rule of thumb to have CONCURRENCY_LEVEL= to reflect the number of cores on the machine building the kernel ?
And use fakeroot (2 core example):
fakeroot make-kpkg -j 2 --arch=amd64 --append-to-version='custom12' --initrd kernel_image kernel_headers > ~/out 2>~/out-error