Bug 9881 - Building intel driver w/o dri causes build to fail
Summary: Building intel driver w/o dri causes build to fail
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: low trivial
Assignee: Eric Anholt
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-05 04:55 UTC by Dag Bakke
Modified: 2007-08-23 01:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dag Bakke 2007-02-05 04:55:59 UTC
With git bits (modesetting branch) as of yesterday morning

# ./configure --prefix=/usr --disable-dri   
[.....]
# make
[......]
 gcc -DHAVE_CONFIG_H -I. -I.. -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -I/usr/include/xorg -DI830_XV -DI830_USE_XAA -DI830_USE_EXA -g -O2 -MT i810_accel.lo -MD -MP -MF .deps/i810_accel.Tpo -c i810_accel.c  -fPIC -DPIC -o .libs/i810_accel.o
In file included from i810.h:54,
                 from i810_accel.c:55:
/usr/include/xf86drm.h:41:17: error: drm.h: No such file or directory
In file included from i810.h:54,
                 from i810_accel.c:55:

If this is expected, perhaps the '--disable-dri' option should be removed?
Comment 1 Daniel Stone 2007-02-27 01:36:11 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 WuNian 2007-08-13 20:39:40 UTC
The bug still exists in the latest intel driver.
Comment 3 Gordon Jin 2007-08-16 19:31:47 UTC
Yes, the '--disable-dri' option should be removed. Thanks for the report.
Comment 4 Wang Zhenyu 2007-08-23 01:54:53 UTC
--disable-dri option is only used when you build intel video driver against xserver without dri enabled, so this isn't a bug, but an option for build.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.