Re: /usr/include/linux, /usr/include/asm, ...
On Tue, 18 Feb 1997, Hamish Moffatt wrote:
> > So, what else are the links good for? Most programs do not
> > (and should not) depend on kernel version specific api's; and the
> > handful that do should ask for and include -I/usr/src/linux anyway.
> Has anyone had any luck compiling (z)ftape 3.02 on debian, then?
> I've tried, but it (reasonably) requires current kernel headers,
> and despite adding the above to several Makefiles, it still
> does not look in /usr/src/linux first.
> Besides, the gcc manual page says: -I "Append directory <dir>
> to the list of directories searched for include files.",
> which implies that -I/usr/src/linux will be added to the
> very end of the search path, after /usr/include; ie this will
> really do nothing except for new (as opposed to updated)
> kernel header files. It certainly does not work for me.
Actually, the correct choice is -I/usr/src/linux/include/
And Include paths that are put on the command line get used before any
standard paths. I use this to my benefit many times. You have to do
this to compile recent modutils, any kernel modules, etc...
Works great if you get the right directory.
----==-- _ / / \
---==---(_)__ __ ____ __ / / /\ \ - email@example.com
--==---/ / _ \/ // /\ \/ / / /_/\ \ \ - firstname.lastname@example.org
-=====/_/_//_/\_,_/ /_/\_\ /______\ \ \ - email@example.com
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com