From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Arador <diegocg@teleline.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: buggy include path?
Date: Tue, 18 Feb 2003 15:39:19 -0800 [thread overview]
Message-ID: <20030218153919.16d41430.rddunlap@osdl.org> (raw)
In-Reply-To: <20030219002938.08b717c7.diegocg@teleline.es>
On Wed, 19 Feb 2003 00:29:38 +0100
Arador <diegocg@teleline.es> 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:
./include/asm-um/irq_vectors.h
./include/asm-i386/mach-default/irq_vectors.h
./include/asm-i386/mach-visws/irq_vectors.h
./include/asm-i386/mach-voyager/irq_vectors.h
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?
Anyone?
--
~Randy
next prev parent reply other threads:[~2003-02-18 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 23:29 Arador
2003-02-18 23:39 ` Randy.Dunlap [this message]
2003-02-19 15:32 ` Sam Ravnborg
2003-02-18 23:47 ` Arador
2003-02-19 15:33 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030218153919.16d41430.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=diegocg@teleline.es \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®