I have a very high respect for Joerg. But please let me comment a little on this.
Back "in the former times" (I started using GNU/Linux back when the only distros were SLS and Slackware), apps assumed that the kernel header files are in a "linux" directory in the system include path (the /usr/include/linux symlink, unless the user has a very strange setup). They need not assume there is anything in /usr/src/linux, though /usr/include/linux is likely a symlink to /usr/src/linux/include/linux. And I have never heard of anyone hard-coding /usr/src/sys (nor have I heard of such a directory at all) in their makefiles. I have never encountered any app that has such an elaborate setup to detect where the kernel include files are; I would tend to say that such elaborate setup is unnecessary. If the system in question is so broken as to not make the kernel include files accessible via a simple #include <linux/some-file.h>, it will have problems compiling all kernel-dependent software, not just cdrtools: Systems that are broken to such an extent do not deserve to be supported by an elaborate makefile system; a simple FAQ entry would suffice. On Sun, Jan 25, 2004 at 07:30:48PM +0100, Joerg Schilling wrote: > You miss that in former times most Linux distributions in > most cases did not include the needed include files at all > in case the Linux kernel sources have not been installed at > /usr/src/linux. The "files" in /usr/include/sys/ have been > sysmlinks pointing to /usr/src/linux. > > Newer Linux systems tend to have real files in /usr/include. > > Some systems have neither symlinks nor files in > /usr/include/sys. > > This is completely chaotic and the setup for Linux in the > makefile system tries to do its best from this desaster..... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]