Does anyone know why one must do make mrproper before building a kernel? Is
it gcc having problems with bad code? I never had to do this on Redhat 6.x,
but it is a must with 7.x.
Forrest
> -----Original Message-----
> From: Chris Kloiber [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 23, 2001 12:57 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Compiling kernel modules...
>
>
> On Mon, 23 Jul 2001, John Leeuw wrote:
>
> > Sounds like I should really run mrproper first!! Haven't
> tried that yet,
> > will do, thanks to everyone for the info! This list rocks!
>
> # cd /usr/src/linux-2.4
>
> # make mrproper
>
> # cp configs/kernel-<whichever_is_closest_to_your_platform> .
>
> # make oldconfig
>
> # make menuconfig (or xconfig)
>
> # vi Makefile
> (change EXTRAVERSION= so you can tell it's your kernel. You
> also get a
> completely seperate and non-conflicting directory of modules!)
>
> # make dep clean bzImage modules modules_install
>
> # cp arch/i386/boot/bzImage /boot/vmlinuz-<your_version>
>
> # cp System.map /boot/System.map-<your_version>
>
> # cd /boot
>
> # ln -sf vmlinuz-<your_version> vmlinuz (optional)
>
> # ln -sf System.map-<your_version> System.map (optional)
>
> # mkinitrd initrd-<your_version>.img <your_version>
> (needed if boot from scsi or using ext3/reiserfs)
>
> # vi /etc/lilo.conf ; lilo -v -v
>
> Hope this helps.
>
> --
> Chris Kloiber, RHCE
> Enterprise Support - Red Hat, Inc.
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
