[Pkg-opencl-devel] Bug#806965: Bug#806965: oclgrind: FTBFS on ppc64el -- conflict with altivec keyword bool

[Rebecca N. Palmer]

> You're right. Upstream needs the local copy since many systems don't
> have recent enough OpenCL headers, but for Debian I could add a patch
> to remove the local copy and have a build-dependency on opencl-headers
> instead.

opencl-headers already has the __vector fix, but as already noted, the 
bool problem is a deeper "this is a keyword in standard C++" issue:

http://sources.debian.net/src/khronos-opencl-headers/2.0~svn32091-1/debian/patches/use__vector.patch

On 08/12/15 21:14, J Price wrote:
> Reading some other bug reports (e.g. [1]) suggests that compiling with
> `-std=gnu++11` instead of `-std=c++11` also fixes the problem. Is this
> a viable workaround? This would be a simple patch to CMakeLists.txt.

Probably; if you want to test on ppc64el there's qemu-debootstrap (~10x 
slower, but shouldn't be a problem for a package this small), 
https://wiki.debian.org/CrossCompiling or the porterbox, but several of 
my FTBFS-on-$arch fixes were uploaded without testing on $arch.