All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 50280] New: Mesa 8.0.3 fails to build dri/nouveau against libdrm 2.4.34
Date: Wed, 23 May 2012 13:10:23 +0000	[thread overview]
Message-ID: <bug-50280-8800@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 50280
           Summary: Mesa 8.0.3 fails to build dri/nouveau against libdrm
                    2.4.34
    Classification: Unclassified
           Product: Mesa
           Version: 8.0
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: high
         Component: Drivers/DRI/nouveau
        AssignedTo: nouveau@lists.freedesktop.org
        ReportedBy: mc2374@mclink.it


Created attachment 62018
  --> https://bugs.freedesktop.org/attachment.cgi?id=62018
Log of a failed build

As per summary.
Building against libdrm 2.4.34 and kernel 3.2.16, Mandriva 2010.2 x86_64.

The message error is:
**************************
In file included from nouveau_fbo.c:27:
nouveau_driver.h:41:28: error: nouveau_device.h: No such file or directory
nouveau_driver.h:42:27: error: nouveau_grobj.h: No such file or directory
nouveau_driver.h:43:29: error: nouveau_channel.h: No such file or directory
nouveau_driver.h:44:24: error: nouveau_bo.h: No such file or directory
nouveau_driver.h:45:30: error: nouveau_notifier.h: No such file or directory
nouveau_driver.h:49:26: error: nv04_pushbuf.h: No such file or directory
In file included from nouveau_screen.c:27:
nouveau_driver.h:41:28: error: nouveau_device.h: No such file or directory
nouveau_driver.h:42:27: error: nouveau_grobj.h: No such file or directory
nouveau_driver.h:43:29: error: nouveau_channel.h: No such file or directory
nouveau_driver.h:44:24: error: nouveau_bo.h: No such file or directory
nouveau_driver.h:45:30: error: nouveau_notifier.h: No such file or directory
nouveau_driver.h:49:26: error: nv04_pushbuf.h: No such file or directory
nouveau_fbo.c: In function ‘nouveau_renderbuffer_storage’:
nouveau_fbo.c:97: error: ‘NOUVEAU_BO_VRAM’ undeclared (first use in this
function)    
nouveau_fbo.c:97: error: (Each undeclared identifier is reported only once
nouveau_fbo.c:97: error: for each function it appears in.)
nouveau_fbo.c:97: error: ‘NOUVEAU_BO_MAP’ undeclared (first use in this
function)
nouveau_fbo.c: In function ‘nouveau_renderbuffer_map’:
nouveau_fbo.c:145: error: ‘NOUVEAU_BO_RD’ undeclared (first use in this
function)     
nouveau_fbo.c:147: error: ‘NOUVEAU_BO_WR’ undeclared (first use in this
function)
nouveau_fbo.c:149: warning: implicit declaration of function ‘nouveau_bo_map’
nouveau_fbo.c:151: error: dereferencing pointer to incomplete type
nouveau_fbo.c: In function ‘nouveau_renderbuffer_unmap’:
nouveau_fbo.c:172: warning: implicit declaration of function ‘nouveau_bo_unmap’ 
nouveau_screen.c:31:27: error: nouveau_drmif.h: No such file or directory
In file included from nouveau_context.c:28:
nouveau_driver.h:41:28: error: nouveau_device.h: No such file or directory
nouveau_driver.h:42:27: error: nouveau_grobj.h: No such file or directory
nouveau_driver.h:43:29: error: nouveau_channel.h: No such file or directory
nouveau_driver.h:44:24: error: nouveau_bo.h: No such file or directory
nouveau_driver.h:45:30: error: nouveau_notifier.h: No such file or directory
nouveau_driver.h:49:26: error: nv04_pushbuf.h: No such file or directory
nouveau_screen.c: In function ‘nouveau_init_screen2’:
nouveau_screen.c:131: warning: implicit declaration of function
‘nouveau_device_open_existing’
nouveau_screen.c:144: error: dereferencing pointer to incomplete type
nouveau_screen.c: In function ‘nouveau_destroy_screen’:
nouveau_screen.c:178: warning: implicit declaration of function
‘nouveau_device_close’
gmake[6]: *** [nouveau_fbo.o] Error 1
gmake[6]: *** Waiting for unfinished jobs....
***********************************

It cannot find all those nouveau_[device | grobj | channel | bo | notifier |
drimif] headers and the nv04_pushbuf.h one because they are no more present in
the libdrm include dir.

The previous release of libdrm (2.4.33) still provides the needed .h files and
obviously works.


See the attached log for more infos.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2012-05-23 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 13:10 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-50280-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-05-28 19:41   ` [Bug 50280] Mesa 8.0.3 fails to build dri/nouveau against libdrm 2.4.34 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 20:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-28 20:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-05-29 18:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-03 20:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-50280-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.