> After a kernel compliation I am no longer able to clean files for a new
> kernel compilation using "make mrproper".
> I recently compiled the Linux-2.0.12 kernel with no noticeable problems,
> but rarely used the 'modules' option in the compilation and so ended up
> with a large kernel (the kernel daemon was compiled into this kernel).
> Problems occurred after a second compilation where the modules option was
> used heavily (PPP, sound, ethernet card etc.) and the kernel daemon
> (kerneld) was compiled into the kernel as before.
> In both cases using the usual process of building a kernel in X-windows:
> cd /usr/include
> rm -rf asm linux scsi
> ln -s /usr/src/linux/include/linux linux
> ln -s /usr/src/linux/include/asm-i386 asm
> ln -s /usr/src/linux/include/scsi scsi
> cd /usr/src/linux
> make mrproper
> make xconfig
> and in each case the following error was flagged:
> WARNING - broken Config.in! CONFIG_AEDSP16 was not declared!
> The kernel was then built using:
> make dep ; make clean
> make zImage
> make modules
> make modules_install
> etc. .....
> In this second kernel compilation I learned that I had been a little
> overzealous in trying to move code out of the kernel into modules
> (some filesystems mounted during boot were not supported from the
> kernel), and the re-boot failed. I re-booted from a boot-floppy and
> moved the first kernel image to /vmlinuz, re-ran /sbin/lilo, and
> then rebooted the first kernel image intending to re-compile the kernel
> using fewer 'module options'.
> However, when running through the above steps the process failed on:
> make mrproper
> with the message:
> no rule to make target: *** mrproper ***
> What may have happened? Has anything similar happened to anyone else
> with this kernel? How should I go about fixing it? I re-loaded the
> kernel source code with the same result as above. Any help would be
> appreciated.
a broken flock () emulation on boot {fcntl_setlk() called by process
##(lpd)} as recommended in /usr/src/linux/Documentation/Changes, so this
may be the source of the problem. I would still appreciate any
suggestions as to how this problem may be fixed.
Nick
--
***********************************************
* *
* Nick Bridgett *
* *
***********************************************