I figured it out myself - I had the wrong option below, should have been<br><br>--with-clanguage=cxx<br><br>although I'm not sure why it didn't work with just gcc.<br><br>Randy M.<br><br><div class="gmail_quote">On Fri, Sep 3, 2010 at 3:20 PM, Randall Mackie <span dir="ltr"><<a href="mailto:rlmackie862@gmail.com">rlmackie862@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm trying to compile a uniprocessor version of my PETSc code on Windows under cygwin.<br>
<br>I just downloaded and installed cygwin plus gcc, g++, and gfortran, and lapack.<br><br>Whenever I run configure, I get the following error message:<br>
<br>$ ./configure PETSC_ARCH=windows-gfortran-serial --with-fortran --with-fortran-kernels=1 --with-scalar-type=co<br>mplex --with-debugging=0 --with-mpi=0 --with-c-language=cxx<br>===============================================================================<br>
Configuring PETSc to compile on your system <br>===============================================================================<br>=============================================================================== WARNING! Compiling PETSc with no debugging, this should only be done for timing and production runs. All development should be done when configured using --with-debugging=1 =============================================================================== TESTING: configureScalarType from PETSc.utilities.scalarTypes(config/PETSc/utilities/scalarTypes.py:36) *******************************************************************************<br>
UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for details):<br>-------------------------------------------------------------------------------<br>C Compiler provided doest not support C99 complex<br>
*******************************************************************************<br><br><br>I've even tried adding the option --CFLAGS='-std=c99', but I get the same error message.<br><br>Anybody have any suggestions for how to get past this?<br>
<br>Thanks, <br><br>Randy M.<br><br><br>
</blockquote></div><br>