Summary: | radeonsi_pipe.c:322:7: error: ‘PIPE_CAP_DUAL_SOURCE_BLEND’ undeclared | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | highest | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Possible patch for removing radeon build
Possible patch for removing nouveau build |
Description
Vinson Lee
2012-04-14 13:16:57 UTC
This error is fixed by commit 69a921892d2303f1400576aa73980c28880f8654 Radeonsi still won't build on Scons, because gallium/drivers/radeon doesn't have a SConscript and libradeon.a is required by radeonsi. We can leave this bug open until that is fixed. I'm fine droping radeon from scons build. Neither of the two build systems (scons / autotools) will go away any time soon, so instead of trying to build evertyhing with both, it makes more sense to focus on the targets/components that truly matter for the scons/autotools users. FWIW, I made patches which remove radeon drivers from the scons build 2 years ago and some people weren't very happy about it. I think we shouldn't support 2 build systems for Linux-only drivers. (In reply to comment #3) > FWIW, I made patches which remove radeon drivers from the scons build 2 > years ago and some people weren't very happy about it. At the time, the make based build system didn't support out-of-tree builds or even reliable parallel builds, both of which have been addressed with automake. Created attachment 78803 [details] [review] Possible patch for removing radeon build Created attachment 78804 [details] [review] Possible patch for removing nouveau build I could also remove the i915 build if it's requested. Fixed by commit 4ca44f2c5e6b3a0a91626b576d72d306e5c08592 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.