Name conflict with preprocessor macro
Issue #315 resolved
We are running into an issue on Power9 systems, where the symbol
VT1 (possibly others) are defined as a macro. This causes compilation of code that includes certain Blaze headers to fails as this symbol is used all over the place as a template argument name. Please see https://github.com/STEllAR-GROUP/phylanx/issues/1088 for details.
FWIW, we have decided to fix our particular issue by adding
#undefdirectives to HPX. This appeared to be the least intrusive fix. Please see here for more details: https://github.com/STEllAR-GROUP/hpx/pull/4322. Thanks!
Commit 7850cb4 prevents all naming conflicts with the preprocessor symbols
VT2. The fix is immediately available via cloning the Blaze repository and will be officially released in Blaze 3.7.
Thanks Klaus! Much appreciated.