Compilation errors on Vortex from mangling issue with `cher`, `cher2`, `zher`, and `zher2`

[MalachiTimothyPhillips]

Compilation errors on Vortex from mangling issue with `cher`, `cher2`, `zher`, and `zher2`

[ndellingwood]

@MalachiTimothyPhillips thanks for reporting and adding the PR! Can you share module/tpl/configuration details that exposed the issue?

[MalachiTimothyPhillips]

@MalachiTimothyPhillips thanks for reporting and adding the PR! Can you share module/tpl/configuration details that exposed the issue?

It was part of a SIERRA/spack Trilinos build on Vortex targeting cuda. Attached is the Spack cmake build output, which should include the CMake flags passed to Trilinos.
spack-build-01-cmake-out.txt

As per the modules, they are what you get if you module load sierra-devel on Vortex:

[malphil@vortex66 ~]$ module load sierra-devel

Lmod is automatically replacing "clang/ibm-16.0.6-cuda-11.2.0-gcc-8.3.1" with "gcc/8.3.1".

module list
Due to MODULEPATH changes, the following have been reloaded:
  1) spectrum-mpi/rolling-release

[malphil@vortex66 ~]$ module list

Currently Loaded Modules:
  1) base-gcc/8.3.1       3) git/2.29.1     5) gcc/8.3.1     7) spectrum-mpi/rolling-release   9) sierra-devel/nvidia
  2) StdEnv         (S)   4) python/3.8.2   6) cuda/11.2.0   8) sntools/master

  Where:
   S:  Module is Sticky, requires --force to unload or purge

I'll also note that we were not able to replicate this on our ascicgpu builds. I wonder if it's some funky combination including the power9 architecture?

[ndellingwood]

@MalachiTimothyPhillips thanks for sharing, that will help us to try and avoid a future slip. I haven't seen this in our nightly integration builds of Trilinos on Power9+V100, we use OpenBLAS for the blas and lapack tpls in those builds, and peaking at your cmake output it looks like your build uses netlib installs, maybe something odd happens within that difference?

[MalachiTimothyPhillips]

@ndellingwood I'm going to go ahead and mark this as closed since #2183 was merged in. Let me know if you want to create a separate issue to see if we can reproduce this compilation error.