From: erc@unislc.uucp (Ed Carp) Subject: Re: Include header (mis)location in 0.97 Date: Fri, 7 Aug 1992 07:21:55 GMT
rghuehn@sunee.uwaterloo.ca (Rob Huehn) writes:
: 0.97 needs several /usr/include/linux/*.h files moved back to their
: normal location in sys before it can be compiled. I've followed the
: gcc installation advice and merged the kernel includes into /usr/include,
: and it seemed work fine for 0.96. Now, in order to use the new 0.97
: includes I symlinked /usr/src/linux/include/sys, etc., into /usr/include.
The instructions for 0.97 cover this; unfortunately, the README wasn't
included in the tar file :(
: The point is, I'm trying to keep one set of include files with any
: kernel-specific files in <linux/*>. Why isn't this the way the kernel
: sources come in the first place? It seems that given a current gcc and
: kernel, everyone should have the same headers, so why not bundle them
: up and put them on an archive site? Right now I don't have much
: confidence that my /usr/include is correct.
The reason that they're separate is because they change from kernel to
kernel. I, like several others, keep multiple kernel source trees
around (for various reasons). My /usr/src/tree looks like:
/usr/src/linux-0.96c
/usr/src/linux-0.97
/usr/src/linux -> /usr/src/linux-0.97
That way, when I need to (for example) build a 0.96c kernel, I just do:
cd /usr/src
rm linux
ln -s linux-0.96c linux
BTW, ps-0.96* is under /usr/src/linux-0.96c, and ps-0.97 is under
/usr/src/linux-0.97. Works for me.
You only have one symlink in /usr/include - /usr/include/linux is linked to
/usr/src/linux/include/linux. That way, you just change the /usr/src/linux
symlink for the currently running kernel, and away you go!
-- Ed Carp, N7EKG erc@apple.com 801/538-0177 "This is the final task I will ever give you, and it goes on forever. Act happy, feel happy, be happy, without a reason in the world. Then you can love, and do what you will." -- Dan Millman, "Way Of The Peaceful Warrior"