From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 55919] New: fatal error: nouveau/nouveau_device.h: No such file or directory
Date: Fri, 12 Oct 2012 13:35:34 +0000 [thread overview]
Message-ID: <bug-55919-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2261 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=55919
Priority: medium
Bug ID: 55919
Assignee: dri-devel@lists.freedesktop.org
Summary: fatal error: nouveau/nouveau_device.h: No such file or
directory
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: spark74@gmx.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: 7.11
Component: Drivers/Gallium/r300
Product: Mesa
After
make linux-x86-64
I got
make[4]: Entering directory
`/remote/lithop4-3/egger/mesa/Mesa-7.11.2/src/gallium/drivers/nvfx'
gcc -c -I. -I../../../../src/gallium/include
-I../../../../src/gallium/auxiliary -I../../../../src/gallium/drivers
-I../../../../src/gallium/drivers/nouveau/include -Wall -Wmissing-prototypes
-Wdeclaration-after-statement -Wpointer-arith -O3 -g -fPIC -m64 -D_POSIX_SOURCE
-D_POSIX_C_SOURCE=199309L -D_SVID_SOURCE -D_BSD_SOURCE -D_GNU_SOURCE -DPTHREADS
-DUSE_XSHM -DHAVE_POSIX_MEMALIGN -DUSE_X86_64_ASM -I/usr/X11R6/include -std=c99
-ffast-math -fno-strict-aliasing nv04_2d.c -o nv04_2d.o
nv04_2d.c:36:36: fatal error: nouveau/nouveau_device.h: No such file or
directory
compilation terminated.
make[4]: *** [nv04_2d.o] Error 1
make[4]: Leaving directory
`/remote/lithop4-3/egger/mesa/Mesa-7.11.2/src/gallium/drivers/nvfx'
make[3]: *** [default] Error 1
make[3]: Leaving directory
`/remote/lithop4-3/egger/mesa/Mesa-7.11.2/src/gallium/drivers'
make[2]: *** [default] Error 1
make[2]: Leaving directory
`/remote/lithop4-3/egger/mesa/Mesa-7.11.2/src/gallium'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/remote/lithop4-3/egger/mesa/Mesa-7.11.2/src'
What is wrong and is it needed to build this gallium drivers if I just want to
have libGL.so and libOSMesa.so?
My linux is Red Hat Enterprise Linux WS release 4 (Nahant Update 8)
and gcc version 4.5.2 (GCC).
I even tried to build libdrm-2.4.39 but there is no nouveau_device.h, too.
I tried to copy a nouveau_device.h from somewhere else but then the next
nouveau-header is missing.
It would be great if you give me an advice.
Kind regards,
Roland
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3561 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 reply other threads:[~2012-10-12 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 13:35 bugzilla-daemon [this message]
2012-10-12 14:15 ` [Bug 55919] fatal error: nouveau/nouveau_device.h: No such file or directory 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
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@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