Re: Recompiling kernel

[Aaron Prohaska <verdesoft verdesoft net>]

I don't remember for sure if I said yes to the development tools or not.
The only way I know of to change it now is to boot the Red Hat install
disk in and choose upgrade. Is there an easier way to do this?

Thanks for the help,

Aaron
> 
> gcc is your C compiler, a (shall we say) essential tool for rebuilding
> your kernel.  The command not found above means it's not in your PATH,
> probably because it isn't installed.  When you installed the system, did
> you say yes to the development tools options?  (In future, install these
> on your system, if you want to do any building of your own, or even
> think you might.  Otherwise, you're dependent on another machine to
> build any specialized binaries...)
> 
> Get out your Redhat disk and start installing.  Let's see here, I've
> never had to piece together the build environment from scratch before.
> Someone may have to second my efforts, since I'll probably forget
> something.
> 
> I'd install: (I'm looking at a RH 5.1 CD, so your version nums may
> differ)
> (It's also on a Win98 machine, so the filenames are mangled.  Gee, I'm
> not much help am I?)
> 
> binutils.rpm
> egcs-1.0.rpm
> egcs-c++.rpm
> gcc-2.7.2.rpm
> gdb-4.17.rpm
> ld.so-xx.x.rpm
> ldconfig.rpm
> libstdc-xx.x.rpm
> make-3.7.rpm
> makedev-xx.rpm
> modutils.rpm
> procps-1.rpm
> procps-x.rpm
> 
> After installing these, just run "gcc -v" at the command line.  If you
> get something about your compiler version, you're in business.  As long
> as I didn't leave something important out above, right?  Then:
> 
> cd /usr/src/linux  (assuming your kernel source is installed)
> make mrproper      (to clean up a bit)
> make menuconfig    (select your kernel options, vfat is under
> "filesystems".  Oh and I'd leave modules for later.  That gets tricky
> for the first time.)
> make dep
> make clean
> make zImage
> 
> If it complains that your kernel is too large, try again with "make
> bzImage."  When it finishes successfully, you can say "make install."
> 
> Then fix lilo.  IMPORTANT: FIRST read man lilo, and man lilo.conf.  Edit
> /etc/lilo.conf, add another stanza for your old kernel, in case the new
> one does not work.  The new kernel should be called vmlinuz, in /boot.
> In lilo.conf, make your old kernel something like vmlinux.old.  This
> way, if your kernel does not boot, you can reboot the machine and press
> <Tab> at the LILO prompt.  All your boot options will be listed:  linux
> linux.old.
> Which reminds me, after editing /etc/lilo.conf, run /sbin/lilo to update
> the boot sector.  Otherwise your changes won't take effect.
> 
> Hope that gets you started.
> 
> Eric Cifreo
> Austin, TX
> 
> "Now there's one hoopy frood who really knows where his towel is."
>                                         --Douglas Adams
> 
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
>                 http://www.redhat.com http://archive.redhat.com
>          To unsubscribe: mail redhat-list-request redhat com with
>                        "unsubscribe" as the Subject.

-- 
_________________________________________________

mailto:verdesoft verdesoft net
VerdeSoft Internet Services
http://www.verdesoft.net/