Very Computer

I've been trying to compile the 2.0.0 kernel that just came out.  So far, all
the code compiles fine, but when it links all of the different .o files into the
final kernel, I get a plethora of unknown function calls (or similar errors) and
it stops.  I am using gcc 2.7.2, g++ 2.7.1.4, libc 5.4.2, binutils 2.6.0.15, and
kernel 1.99.14.  There are too many error messages to really catch for including
in this posting, but I can get them if need be.  Has anyone else had problems
compiling the 2.0 kernel.  I used the same configuration options as in the
previous compile (yes, I did remake the config files with the 2.0 menuconfig
scripts) and everything seems to work with that kernel.

Also another minor problem - I can't seem to get any messages posted to the
linux.dev.kernel newsgroups.  Am I doing something wrong, or is my server fubar?

Joe Miller

: I've been trying to compile the 2.0.0 kernel that just came out.  So far, all
: the code compiles fine, but when it links all of the different .o files into the
: final kernel, I get a plethora of unknown function calls (or similar errors) and
: it stops.  I am using gcc 2.7.2, g++ 2.7.1.4, libc 5.4.2, binutils 2.6.0.15, and
: kernel 1.99.14.  There are too many error messages to really catch for including
: in this posting, but I can get them if need be.  Has anyone else had problems
: compiling the 2.0 kernel.  I used the same configuration options as in the
: previous compile (yes, I did remake the config files with the 2.0 menuconfig
: scripts) and everything seems to work with that kernel.

        I had that same problem the first time I tried to compile 2.0.
Here is what you should do:

* Delete all your old source code in the /usr/src/ directory. Especially
make sure you delete any symbolic link you have (ex. /usr/src/linux) that
might take you to "/usr/src/linux-1.2.13/". After I deleted all my old
source code the installation worked fine.

* Have the tar file in the /usr/src/ directory, then untar it with the -xf
extensions (-v if you like to see all the files it writes). It will
deposite all of the code in the /usr/src/linux/ directory.

* Then just follow everything they say to do in the README file, including
the "mrproper" command, and the "make deps ; make clean" command.

Kevin
Cols, Oh