From: jefftep@cs.utexas.edu (Jeffrey Grills) Subject: Re: 0.99.2 compile problem Date: 7 Jan 1993 02:41:38 -0600
In article <C0Fw86.E2t@ppcger.ppc.sub.org> sepp@ppcger.ppc.sub.org (Josef Wolf) writes:
>torvalds@klaava.Helsinki.FI (Linus Torvalds) writes:
>>I've now seen two compilation problem reports, and they both looked like
>>being due to bad include-file setups, probably due to a problem with the
>>SLS files.
>
>>IMPORTANT! To get any linux kernel to compile, your /usr/include/linux
>>and /usr/include/asm directories should be symlinks to the linux
>>include-dirs. If they aren't, correct the problem with:
>
>> # rm -rf /usr/include/linux
>> # rm -rf /usr/include/asm
>> # ln -s /usr/src/linux/include/linux /usr/include/linux
>> # ln -s /usr/src/linux/include/asm /usr/include/asm
>
>This problem originates in the new include-files as packaged in inc-4.2.TZ.
[...]
>Greetings
> Sepp
>
>--
>sepp@ppcger.ppc.sub.org
>Josef Wolf, Germersheim, Germany
>..!ira.uka.de!smurf.sub.org!ppcger.ppc.sub.org
SLS comes (at least did come) with the links backwards.
if you did a
cd /usr/src
rm -r linux
tar zxvf linux.tar.Z
and didn't have your sym links correct, you ended up with
the old headers in /usr/inlude/{asm,linux}. Thid happened to me.
In my case, the kernel compiled just fine, but refused to
boot. much harder to find than these errors where the comiler
balks. Perhaps we can make it always balk with the wrong header
files... maybe an
#define LINUX_0_99_2
in one of the header files, and then in some real kernel source,
#ifndef LINUX_0_99_2
# error wrong header files being used to compile
#endif
Just an idea to maybe save new users (and ourselves) some problems.
-- jeff grills jefftep@cs.utexas.edu