From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: tim <tim@holymonkey.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: include/asm/irq_vectors.h not found
Date: Wed, 2 Oct 2002 23:08:48 +0200 [thread overview]
Message-ID: <20021002210848.GE1883@ppc.vc.cvut.cz> (raw)
In-Reply-To: <20021002135939.129a6a5f.tim@holymonkey.com>
On Wed, Oct 02, 2002 at 01:59:39PM -0700, tim wrote:
> when installing dri drivers for my gfx card (r200-20020927-linux.i386) i get the following error during kernel module compilation:
VMware suffers from same problem. Because of I do not support VMware
on SGI visual workstation, I now use an additional
-I/lib/modules/`uname -r`/build/arch/i386/mach-generic
in vmmon/vmnet Makefile, and for 2.5.x it is required to have full kernel
source installed, not only kernel-headers package (if there is some distro
that distributes kernel-headers 2.5.x package...).
> cc -O2 -Wall -Wwrite-strings -Wpointer-arith -Wcast-align -Wstrict-prototypes -Wnested-externs -Wpointer-arith -D__KERNEL__ -DMODULE -fomit-frame-pointer -DCONFIG_AGP -DCONFIG_AGP_MODULE -DCONFIG_DRM_SIS -DMODVERSIONS -include /lib/modules/2.5.39/build/include/linux/modversions.h -DEXPORT_SYMTAB -I/lib/modules/2.5.39/build/include -c radeon_drv.c -o radeon_drv.o
> In file included from /lib/modules/2.5.39/build/include/linux/irq.h:19,
> from /lib/modules/2.5.39/build/include/asm/hardirq.h:6,
> from /lib/modules/2.5.39/build/include/linux/interrupt.h:44,
> from drm_os_linux.h:3,
> from drmP.h:75,
> from radeon_drv.c:32:
> /lib/modules/2.5.39/build/include/asm/irq.h:16: irq_vectors.h: No such file or directory
> make: *** [radeon_drv.o] Error 1
I think that behavior should be changed. irq_vectors.h (and eventually other .h) should
be moved to include/asm-i386/irq_vectors-generic.h (or irq_vectors-visws.h) and irq_vectors.h
should be either appropriate symlink, or simple
#ifdef CONFIG_VISWS
#include <irq_vectors-visws.h>
#else
#include <irq_vectors-generic.h>
#endif
Or vendors should be taught to install properly configured kernel-sources by default,
so that we can use (cd /lib/modules/`uname -r`/build; make SUBDIRS=`pwd` modules) (or how
it works in 2.5.x kbuild) instead of just trying to guess compiler, compiler options
and include paths because of by default vendors's sources are configured for something
else than running kernel (f.e. -Xcustom instead of -X in EXTRAVERSION in main makefile).
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next prev parent reply other threads:[~2002-10-02 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 20:59 tim
2002-10-02 21:08 ` Petr Vandrovec [this message]
2002-10-02 21:22 ` 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=20021002210848.GE1883@ppc.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@holymonkey.com \
/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®