magarity
asked on
recompile for 386 --- not!
After installing slackware 7.1 on a hard drive in a P2 and moving the drive to a 386DX with a 387, the kernel (2.2) panics with 'recompile for a 386!'. So I put the drive back in the P2, select all the 386 related options and compile with 'make bzlilo'.
The kernel gives the same complaint back in the 386 every time. Is there some option that I might be missing that isn't in the 'processor options' section of the kernel's make config? Or does something else special need to be done when compiling on one platform and moving to another? I've done this successfully with a MUCH older slackware distro without any special changes between the P2 and the 386, but something is stopping this particular release.
Thanks for any help,
magarity
The kernel gives the same complaint back in the 386 every time. Is there some option that I might be missing that isn't in the 'processor options' section of the kernel's make config? Or does something else special need to be done when compiling on one platform and moving to another? I've done this successfully with a MUCH older slackware distro without any special changes between the P2 and the 386, but something is stopping this particular release.
Thanks for any help,
magarity
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah, that actually worked... From a blank install, where the heck was it getting the wrong CPU type info??? Anyway, thanks for the tip; my little firewall box is now on a 2.4.4 kernel, whee!
It got the incorrect CPU type because the kernel source tree had been used to compile a kernel before it was packaged for distribution. Whether the kernel should be distributed that way or not is something of a moot question. The kernel building docs that I've seen all say to do a "make mrproper" the first time you build a kernel and each time that you change the CPU type or mode.
ASKER