Praedor Tempus wrote on Thu, Sep 12, 2002 at 08:44:57AM -0500 : > I run into this problem often, though not all the time. I go through and
<sigh> REAME attached.
--
...and I will strike down upon thee with great vengeance and furious
anger, those who attempt to poison and destroy my binaries, and you
will know my name is root, when I lay my vengeance upon thee.
Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-9mdk
Mandrake Kernel Compile Special Instructions
Due to the way that Mandrake generates multiple versions of the kernel
(uniprocessor, smp, enterprise, boot, secure), recompiling the kernel
from the kernel source installed in /usr/src/linux *MUST* be preceded
by one step:
make mrproper
This is roughly equivalent to "make distclean", but not quite. The
best explanation of why this scenario exists appeared in the Cooker
Mailing List by Andrej Borsenkow:
PLEASE do not forget - you must not need to configure your kernel
before you compile EXTERNAL module (as example, nVidia). PLEASE
remember that Mandrake has 5 (five!) kernel flavours and you can
compile external modules for any of them WITHOUT RECONFIGURATION
IN BETWEEN. PLEASE look into this "regenrated files" in clean
kernel-source and after you have reconfigured your kernel.
To summarize, the kernel source tree is left in a state such that you
compile custom kernel modules for any of the five versions of the
kernel without having to do anything special. One of the side effects
of this is that if you want to start a compile from scratch, you must
remove various configuration files (as well as object files and
binaries). To do this, you *MUST* do the "make mrproper" first.
Regards, the MandrakeSoft Team
msg57759/pgp00000.pgp
Description: PGP signature
