From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 55919] fatal error: nouveau/nouveau_device.h: No such file or directory
Date: Sun, 14 Oct 2012 11:19:25 +0000 [thread overview]
Message-ID: <bug-55919-502-FtoQJGhgdI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-55919-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 604 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=55919
--- Comment #5 from Christoph Bumiller <e0425955@student.tuwien.ac.at> ---
It's an old version of mesa so you need an old version of libdrm if you want to
build nouveau, 2.4.33 or earlier in this case. You can also keep the headers
and libdrm_nouveau.so of both old and new versions installed if you want.
But if you don't want to build nouveau anyway, disable/don't enable it with the
configure script (--with-gallium-drivers=...). It shouldn't even be selected by
default.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1423 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-10-14 11:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 13:35 [Bug 55919] New: fatal error: nouveau/nouveau_device.h: No such file or directory bugzilla-daemon
2012-10-12 14:15 ` [Bug 55919] " bugzilla-daemon
2012-10-12 14:19 ` bugzilla-daemon
2012-10-12 14:26 ` bugzilla-daemon
2012-10-13 17:00 ` bugzilla-daemon
2012-10-14 11:19 ` bugzilla-daemon [this message]
2012-10-15 7:35 ` bugzilla-daemon
2012-10-15 8:20 ` bugzilla-daemon
2012-10-15 8:42 ` bugzilla-daemon
2012-10-15 8:52 ` bugzilla-daemon
2012-12-05 21:36 ` bugzilla-daemon
2012-12-08 22:43 ` bugzilla-daemon
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=bug-55919-502-FtoQJGhgdI@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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