- Original Message -
Building on RHEL6 tinderbox, we get -std=c99, and the radeon uvd code
uses anonymous unions which this disables.
It doesn't look too difficult to fix, just wondering if there was a
reason for using anon unions in the first place?
FWIW, anonymous unions are a
Am 26.04.2013 08:48, schrieb Jose Fonseca:
- Original Message -
Building on RHEL6 tinderbox, we get -std=c99, and the radeon uvd code
uses anonymous unions which this disables.
It doesn't look too difficult to fix, just wondering if there was a
reason for using anon unions in the
On Fri, Apr 26, 2013 at 4:48 PM, Jose Fonseca jfons...@vmware.com wrote:
- Original Message -
Building on RHEL6 tinderbox, we get -std=c99, and the radeon uvd code
uses anonymous unions which this disables.
It doesn't look too difficult to fix, just wondering if there was a
reason
- Original Message -
On Fri, Apr 26, 2013 at 4:48 PM, Jose Fonseca jfons...@vmware.com wrote:
- Original Message -
Building on RHEL6 tinderbox, we get -std=c99, and the radeon uvd code
uses anonymous unions which this disables.
It doesn't look too difficult to fix,
Am 26.04.2013 10:56, schrieb Jose Fonseca:
- Original Message -
On Fri, Apr 26, 2013 at 4:48 PM, Jose Fonseca jfons...@vmware.com wrote:
- Original Message -
Building on RHEL6 tinderbox, we get -std=c99, and the radeon uvd code
uses anonymous unions which this disables.
It
Building on RHEL6 tinderbox, we get -std=c99, and the radeon uvd code
uses anonymous unions which this disables.
It doesn't look too difficult to fix, just wondering if there was a
reason for using anon unions in the first place?
Dave.
___
mesa-dev