According to Phil Deane: While burning my CPU.
>
>
> Hi Folks
>
> First of all let me apoligize for everyone havinging to download the
> attachment to this email.
>
> The problem is:
>
> When I first installed Linux (Slackware 3.5, 2.0.34) I recompiled my
> kernel without any problems, then in a stroke of insanity I decided to
> include sound support and must have chosen a few different or wrong
> settings. and I got errords during compiling.
>
> To get around this I downlaoded the source for 2.0.35 and installed that
> ok, but then I wanted to include parelell printing suport but whne i
> recompiled it I got the same errors. and I am not sure what to do. I
> boot from a floppy so, i can still boot but i would like to have my
> kernel compiled properly. I have one possibly theory as to why this
> happens, and thin it might possible be that the old config is still
> being used, and that is why, but surely if I installed fresh source it
> would have the defualt config??
>
Normaly speaking when one installs new kernel source, one would make a new
directory in /usr/src, take you for example you have obtained 2.0.35 so one
would do much like the following;
cd /usr/src
mkdir linux-2.0.35
rm linux (thats a symlink pointing to your 2.0.34)
ln -s linux-2.0.35 linux (links the new (still empty) directory to "linux")
tar xvzf /path/to/linux-2.0.35.tar.gz
Where /path/to/ would be the path to the directory where the tar archive
is situated.
cd linux
check that the symlinks as per /usr/src/linux/README
make mrproper
make config (menuconfig xconfig)
make zdisk
make modules modules_install
> Anyway I have included the output from the compilation so hopefully
> someone out there will be bale to help me :)
Well i will stick my neck out and say, your using a version of gcc above
2.7.2.x
I use 2.7.2.1 and have never had any problems with kernels up to
2.0.36-pre12
>
> Thanks in advance
> Phil
> The Miracle Express
--
Regards Richard.
[EMAIL PROTECTED]
