[petsc-dev] source code and configure don't know what each other is doing?

[Barry Smith]

  configure looks for complex but source code uses _Complex. Come guys this is 
just absurd.  How can we make sure our configure tests actually have something 
to do with the real usage?


TEST checkC99Complex from 
config.types(/sandbox/petsc/petsc.clone-2/config/BuildSystem/config/types.py:106)
TESTING: checkC99Complex from 
config.types(/sandbox/petsc/petsc.clone-2/config/BuildSystem/config/types.py:106)
  Check for complex numbers in in C99 std
Executing: mpicc -c -o /tmp/petsc-t5CRsd/config.types/conftest.o 
-I/tmp/petsc-t5CRsd/config.libraries -I/tmp/petsc-t5CRsd/config.compilers 
-I/tmp/petsc-t5CRsd/config.setCompilers -I/tmp/petsc-t5CRsd/config.headers 
-I/tmp/petsc-t5CRsd/PETSc.utilities.cacheDetails 
-I/tmp/petsc-t5CRsd/config.functions -I/tmp/petsc-t5CRsd/config.types -std=c89 
-pedantic -Wno-long-long -fPIC -g3 -O0  
/tmp/petsc-t5CRsd/config.types/conftest.c 
Successful compile:
Source:
#include "confdefs.h"
#include "conffix.h"
#include <complex.h>

int main() {
double complex x;
 x = I;
;
  return 0;
}

#elif defined(PETSC_USE_REAL_DOUBLE)
typedef double _Complex PetscComplex;