Andreas Beckmann <[email protected]> wrote on 08/12/2015 17:09:58: > From: Andreas Beckmann <[email protected]> > To: J Price <[email protected]> > Cc: Fernando Seiti Furusato/Brazil/IBM@IBMBR, [email protected], Breno > Henrique Leitao/Brazil/IBM@IBMBR > Date: 08/12/2015 17:10 > Subject: Re: Bug#806965: oclgrind: FTBFS on ppc64el -- conflict with altivec > keyword bool > > On 2015-12-08 20:00, J Price wrote: > >> I don't really like the idea of manipulating unrelated defines in > >> headers ... > > > > OK, so how about if I do this from the .cpp files instead? e.g. > > That would be fine, since it's limited to oclgrind. Doing it in a > (public) header could "contaminate" other projects that include the > header, also it may depend on the order of the includes whether > compilation fails or succeeds. >
Just FYI. Not sure if they are public headers or not, but doing so on headers: src/runtime/icd.h src/core/common.h Made it build for me. Right below #include "CL/cl.h" I included this: #ifdef __ALTIVEC__ # undef bool # undef vector # undef pixel #endif I tried adding to the .cpp files (not all of them) but it didn't work. The headers above are the ones that actually use cl.h. Regards. Fernando
