Re: 2.4.21 not compiling
On Tue, 1 Jul 2003 21:44:07 +1000
"SYNeR" <tups77@tsn.cc> wrote:
> After I let this compile run, I checked / , and saw that the kernel had
> not in fact been updated like it was supposed to (before, it installed it
> to / for me, then pointed the vmlinuz to the new kernel, and vmlinuz.old
> to the old kernel all automatically)...'
> What am I missing here?
No way to tell.
Before you reboot, make sure you have a boot floppy/CD that you can use if
you screw up lilo!
Does /usr/src/linux/arch/i386/boot/bzImage exist? How about
/usr/src/linux/System.map? If they do the kernel was created.
Does /lib/modules/2.4.21 exist, and does it contain modules? If so "make
modules" and "make modules_install" must have worked.
Does /boot/vmlinuz have a time stamp that indicates it is your new kernel?
If all of these look ok, try running /sbin/lilo again.
If not try again, but not all in one step.
Move /usr/src/.config to another name, then do "make mrproper", then move
your config back to /usr/src/.config.
Then do "make dep".
When you do "make bzImage" redirect the output to a file:
make bzImage 2>&1 /usr/src/make.messages
After the compile finishes, examine make.messages to see if you have
indications the kernel didn't build properly. (Hint: Asterisks are bad. More
asterisks are worse.) It's common to have lots of compiler warnings; they
aren't good, but they're usually finger-wagging at the programmer(s) rather
than serious issues.
If you don't see big trouble in make.messages don't worry about modules and
modules_install; if you didn't nuke /lib/modules/2.4.21 they're still there.
Do "make install 2>&1 /usr/src/make.messages"; examine make.messages as
before. If you don't see any problems check /boot/vmlinuz and /vmlinuz
again.
If they're OK you should be ready to reboot.
By the time you figure out why the process didn't work the first time around
you'll understand the basic kernel build/install process (maybe you already
do). Now try The Debian Way:
http://newbiedoc.sourceforge.net/system/kernel-pkg.html
Kevin
Reply to: