From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 45473] New: vdpau-r300 requires softpipe
Date: Wed, 01 Feb 2012 01:36:51 +0000 [thread overview]
Message-ID: <bug-45473-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=45473
Bug #: 45473
Summary: vdpau-r300 requires softpipe
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: neotheuser@ymail.com
When compiling vdpau-r300 (libvdpau_r300.so) I get a compiling error:
No rule to make target
`../../../../src/gallium/drivers/softpipe/libsoftpipe.a', needed by
`../../../../lib/gallium/libvdpau_r300.so'. Stop.
The solution:
Instead of ./autogen.sh --with-dri-drivers="" --with-gallium-drivers=r300
--enable-vdpau
add swrast to gallium driver
./autogen.sh --with-dri-drivers="" --with-gallium-drivers=r300,swrast
--enable-vdpau
Compiles fine now and without error.
Should gallium targets for real hardware use softpipe code / is it necessary?
If so, maybe move the necessary code from softpipe into a common directory
which other gallium targets can easily find, without having to build a whole
new gallium driver such as softpipe to satisfy dependencies.
Reported by Alec Ari <neotheuser@ymail.com>
--
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-02-01 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:36 bugzilla-daemon [this message]
2013-01-11 9:45 ` [Bug 45473] vdpau-r300 requires softpipe 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-45473-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;
as well as URLs for NNTP newsgroup(s).