From: H.J. Lu (hlu@luke.eecs.wsu.edu)
Date: 01/07/93


From: hlu@luke.eecs.wsu.edu (H.J. Lu)
Subject: Re: 0.99.2 compile problem
Date: Thu, 7 Jan 1993 10:10:14 GMT

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.
>There are these two links set up to point to
>
>/net/irl/users/hlu/local/{asm|linux}
>
>or some such. Maybe the maintainor of this package could set up these links
>(and the Makefiles etc/pp) to be correct for the target-machines before
>posting them? This coud save some trouble for some people and some typing
>for other people who are kind enough to answer questions.
>

In release.libc-4.2, there is a warning about that. Maybe it is not
clear enough.

If you have /usr/include/asm and /usr/include/linux set up right before
you install inc-4.2.TZ,

tar xvvofz inc-4.2.TZ

should not touch their symbolic links, at least this is the case for
GNU tar I am using.

H.J.