From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26994] New: Openchrome r839 does not build. Changes required in via_drm.h
Date: Wed, 10 Mar 2010 04:04:27 -0800 (PST) [thread overview]
Message-ID: <bug-26994-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26994
Summary: Openchrome r839 does not build. Changes required in
via_drm.h
Product: DRI
Version: unspecified
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: high
Component: DRM/Via
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: gvlists@gmx.com
This is related to ticket 357 in Openchrome.
http://www.openchrome.org/trac/ticket/357#comment:9
The latest SVN trunk openchrome does not build in Ubuntu 9.04 Jaunty (kernel
2.6.28). The solution suggested by openchrome guys is to add <stdint.h> in
libdrm.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-10 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 12:04 bugzilla-daemon [this message]
2010-03-10 13:26 ` [Bug 26994] xf86-video-openchrome does not build against >=libdrm-2.4.17 bugzilla-daemon
2010-03-10 13:33 ` bugzilla-daemon
2010-03-10 13:33 ` bugzilla-daemon
2010-03-23 17:59 ` bugzilla-daemon
2010-03-29 15:19 ` bugzilla-daemon
2010-05-12 17:42 ` 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-26994-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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