dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 15 Oct 2012 08:42:46 +0000	[thread overview]
Message-ID: <bug-55919-502-PCinJtJXRI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-55919-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1986 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=55919

--- Comment #8 from Roland Egger <spark74@gmx.de> ---
I tested configure and had to install
glproto-1.4.16, dri2proto-2.8 and libdrm-2.4.24 and set the PKG_CONFIG_PATH

Afterwards configure fails with
checking for llvm-config... no
configure: error: LLVM is required to build Gallium R300 on x86 and x86_64

There is a nice configure option
  --enable-gallium-llvm   build gallium LLVM support [default=enabled on
                          x86/x86_64]
Is it possible to disable that option? Trying 
--disable-gallium-llvm does not help

I succeeded with the configure optio
--with-gallium-drivers=""
and recieved
        prefix:          /tmp/Mesa
        exec_prefix:     ${prefix}
        libdir:          ${exec_prefix}/lib
        includedir:      ${prefix}/include

        OpenGL:          yes (ES1: no ES2: no)
        OpenVG:          no

        Driver:          dri
        OSMesa:          no
        DRI drivers:     i915 i965 mach64 mga nouveau r128 r200 r300 r600
radeon savage tdfx unichrome swrast
        DRI driver dir:  ${libdir}/dri
        Use XCB:         no
        Shared dricore:  no

        GLU:             yes
        GLw:             yes (Motif: no)
        glut:            no

        EGL:             yes
        EGL platforms:   x11
        EGL drivers:     builtin:egl_glx

        llvm:            no

        Gallium:         no

        Shared libs:     yes
        Static libs:     no

        CFLAGS:          -g -O2 -Wall -Wmissing-prototypes -std=c99 -ffast-math
-fno-strict-aliasing -fPIC
        CXXFLAGS:        -g -O2 -Wall -fno-strict-aliasing -fPIC
        Macros:          -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN
-DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING
-DGLX_INDIRECT_RENDERING -DHAVE_ALIAS -DUSE_X86_64_ASM

        PYTHON2:         python2

        Run 'gmake' to build Mesa

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2794 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

  parent reply	other threads:[~2012-10-15  8:42 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
2012-10-15  7:35 ` bugzilla-daemon
2012-10-15  8:20 ` bugzilla-daemon
2012-10-15  8:42 ` bugzilla-daemon [this message]
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-PCinJtJXRI@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