[lkml]   [2003]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: buggy include path?
On Wed, 19 Feb 2003 00:29:38 +0100
Arador <> wrote:

| Including include/usb.h from a external module source (out of the kernel tree)
| causes this:
| In file included from /home/diego/kernel/unsta/include/linux/irq.h:19,
| from /home/diego/kernel/unsta/include/asm/hardirq.h:6,
| from /home/diego/kernel/unsta/include/linux/interrupt.h:9,
| from /home/diego/kernel/unsta/include/linux/usb.h:15, <- file included
| from w9968cf.h:38,
| from w9968cf.c:57:
| /home/diego/kernel/unsta/include/asm/irq.h:16:25: irq_vectors.h: No such file or directory
| However in include/asm/irq.h you can see:
| #include <linux/config.h>
| #include <linux/sched.h>
| /* include comes from machine specific directory */
| #include "irq_vectors.h"
| so who is wrong here? This include cames out
| of the specific machine directory; but it doesnt
| seems a wrong include.
| irq_vectors.h is at: include/asm-i386/mach-default/irq_vectors.h

Actually it's in several places:

and where it's included from is decided in linux/arch/i386/Makefile:
for example:
mflags-y += -Iinclude/asm-i386/mach-default

so the include directory is relative (ISTM).
Can the -Idirname be made more complete, e.g. by using
$TOPDIR or $MODLIB ... me wonders.
Or would that just be duplicating the default behavior?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.037 / U:4.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site