[petsc-users] Trying to compile PETSC in cygwin

[Randall Mackie]

I figured it out myself - I had the wrong option below, should have been

--with-clanguage=cxx

although I'm not sure why it didn't work with just gcc.

Randy M.

On Fri, Sep 3, 2010 at 3:20 PM, Randall Mackie <rlmackie862 at gmail.com>wrote:

> I'm trying to compile a uniprocessor version of my PETSc code on Windows
> under cygwin.
>
> I just downloaded and installed cygwin plus gcc, g++, and gfortran, and
> lapack.
>
> Whenever I run configure, I get the following error message:
>
> $ ./configure PETSC_ARCH=windows-gfortran-serial --with-fortran
> --with-fortran-kernels=1 --with-scalar-type=co
> mplex --with-debugging=0 --with-mpi=0 --with-c-language=cxx
>
> ===============================================================================
>              Configuring PETSc to compile on your
> system
>
> ===============================================================================
> ===============================================================================
> 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)
> *******************************************************************************
>          UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for
> details):
>
> -------------------------------------------------------------------------------
> C Compiler provided doest not support C99 complex
>
> *******************************************************************************
>
>
> I've even tried adding the option --CFLAGS='-std=c99', but I get the same
> error message.
>
> Anybody have any suggestions for how to get past this?
>
> Thanks,
>
> Randy M.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20100903/eaa76f65/attachment.htm>