Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
So wrote prosolutions at gmx.net on Friday, 9 September 2005: > Date: Fri, 9 Sep 2005 13:04:18 -0700 > From: prosolutions at gmx.net > To: drbd-user at lists.linbit.com > Subject: [DRBD-user] make kernel-patch failure with 2.6.13 kernel > User-Agent: Mutt/1.5.10i > > > Hi all, > > Since I'm building a kernel for production machines on another system my > understanding is that this can only be done via the 'make KDIR=... kernel-patch' mechanism since 'make; make install' would obviously not make sense on the build system itself. > > But I am getting the following error when I try to compile the kernel-patch: > > > # make KDIR=/usr/src/linux-2.6.13 kernel-patch > make -C drbd drbd_buildtag.c > make[1]: Entering directory `/usr/local/src/drbd-0.7.13/drbd' > make[1]: Leaving directory `/usr/local/src/drbd-0.7.13/drbd' > set -o errexit; \ > kbase=$(basename /usr/src/linux-2.6.13); \ > d=patch-$kbase-drbd-0.7.13; \ > test -e $d && cp -fav --backup=numbered $d $d; \ > bash scripts/patch-kernel /usr/src/linux-2.6.13 . > $d > `patch-linux-2.6.13-drbd-0.7.13' -> `patch-linux-2.6.13-drbd-0.7.13.~1~' > cp: cannot stat `/usr/src/linux-2.6.13/arch/um/Kconfig_block': No such file or directory > make: *** [kernel-patch] Error 1 > > I have a target kernel in /usr/src/linux-2.6.13 which I've configure with 'make menuconfig' > I should maybe add that I'm running this in a chrooted Debian Sarge environment (running under Debian Sid). I don't know if perhaps the chroot could be screwing up the make scripts in detecting the architecture. Because its saying "cannot stat `/usr/src/linux-2.6.13/arch/um/Kconfig_block" it makes me think that maybe its trying to build for architecture "um" for some reason?