Compiling the 2.0.39 kernel with a current distro?

Compiling the 2.0.39 kernel with a current distro?

Post by James Stewar » Sun, 16 Jun 2002 14:22:27



I've never had any trouble compiling the Linux 2.2.x or 2.4.x series kernels
before. I'm now trying to compile the vintage 2.0.39 kernel and the whole
procedure is giving me fits!

I downloaded it from kernel.org

First I did the usual, "make xconfig" and selected what I wanted.

Next I did the "make dep" and it bombed out in the /drivers/char directory
with an "*** [fastdep] Error 135" error.

After messing around with it trying different configs, all with the same
results. I decided to patch the kernel with the "latest 2.0.40-pre 4" patch.

This time the "make dep" was successful!

So I did the "make clean" just to play it safe.

Then the "make bzImage"
But I started getting errors that said "Invalid `asm' statement:"
and "fixed or forbidden register [some machine register] was spilled for
[some class] "

I am compiling this on a Slackware-8 machine (gcc version 2.95.3) that has
successfully compiled other kernels.

So what is the trick to this?

Oh, and no, I'm not going to attempt to use this kernel with Slack-8.  I'm
compiling it to upgrade MuLinux's 2.0.36 so it will read EXT2 filesystems
created in the "sparse inode spacing" mode.  2.0.39 is said to be able to do
this.
=========================

I posted this message earlier to the the Slackware newsgroups, and so far
they seem to think that you have to use an old version of  Linux to compile
this thing.  What a pain!  Is this true?

 
 
 

Compiling the 2.0.39 kernel with a current distro?

Post by Billy O'Conno » Sun, 16 Jun 2002 14:46:35



> I've never had any trouble compiling the Linux 2.2.x or 2.4.x series kernels
> before. I'm now trying to compile the vintage 2.0.39 kernel and the whole
> procedure is giving me fits!

> I posted this message earlier to the the Slackware newsgroups, and so far
> they seem to think that you have to use an old version of  Linux to compile
> this thing.  What a pain!  Is this true?

I always had to use an old compiler for an old kernel, I could never
get the old kernels to compile with the latest gcc.

--
Billy O'Connor
.GNET package maintainer        
360 degrees of portability,
that's business with .GNET