From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52563] New: build failure - struct radeon_renderbuffer has no member named Base
Date: Fri, 27 Jul 2012 04:16:21 +0000 [thread overview]
Message-ID: <bug-52563-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=52563
Bug #: 52563
Summary: build failure - struct radeon_renderbuffer has no
member named Base
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/r200
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: ullysses.a.eoff@intel.com
mesa fails to compile with latest master commit as of
http://cgit.freedesktop.org/mesa/mesa/commit/?id=0e893b42610a2e8f2797bd7da68669dac38d9538
using the following config setup:
./autogen.sh --enable-gles2 --disable-gallium-egl
--with-egl-platforms=x11,wayland,drm --enable-gbm --enable-shared-glapi
error output is:
radeon_span.c: In function 'radeon_renderbuffer_map':
radeon_span.c:70:5: error: 'struct radeon_renderbuffer' has no member named
'Base'
Last known good commit is
http://cgit.freedesktop.org/mesa/mesa/commit/?id=148c8e639da7ee10fc9e002e3c6d60e17d218b21
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-07-26 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 4:16 bugzilla-daemon [this message]
2012-07-27 4:58 ` [Bug 52563] build failure - struct radeon_renderbuffer has no member named Base bugzilla-daemon
2012-07-27 5:08 ` 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-52563-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