Compiling PETSc with Visual Studio 2008

Dear Satish, Thanks for all your helpful comments. I am currently doing a 32 bit build. I will try to install MPICH2 binaries and report the results. I read a bit the manual of latest MPICH2; it says you can build it very easily under windows. I still cannot understand why Matt wrote: MPICH

Compiling PETSc with Visual Studio 2008

On Wed, 23 Apr 2008, Farshid Mossaiby wrote: Dear Satish, Thanks for all your helpful comments. I am currently doing a 32 bit build. I will try to install MPICH2 binaries and report the results. I read a bit the manual of latest MPICH2; it says you can build it very easily under

Compiling PETSc with Visual Studio 2008

Dear Satish, PETSc configure cannot build it with the option --download-mpich=1 [or the alternate mpi with --download-lam=1]. If you know how to build it yourself, and then configure PETSc with it - then that should work. No one has attempted this on windows yet [as far as I know]. Why

Compiling PETSc with Visual Studio 2008

I built PETSc with this command line after installing latest MPICH2: ./config/configure.py --with-cc='win32fe cl --nodetect' --with-fc=0 --with-ar='win32fe lib --nodetect' PETSC_ARCH=cygwin-c-debug-mpi --with-mpi=1 --with-mpi-dir=/cygdrive/c/Program\ Files/MPICH2/

Compiling PETSc with Visual Studio 2008

On Wed, 23 Apr 2008, Farshid Mossaiby wrote: I built PETSc with this command line after installing latest MPICH2: ./config/configure.py --with-cc='win32fe cl --nodetect' --with-fc=0 --with-ar='win32fe lib --nodetect' PETSC_ARCH=cygwin-c-debug-mpi --with-mpi=1

removing f77 support from PETSc?

Since there are two seemingly ok free f90 compilers is there any reason for PETSc to continue to support f77 or should we remove this support, for example change VecGetArrayF90() to VecGetArray() etc and combine the *.h and *.h90 files? I think so. Should we go further and move

removing f77 support from PETSc?

. -- next part -- An HTML attachment was scrubbed... URL: http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20080423/cce01a1a/attachment.html

removing f77 support from PETSc?

that cannot go into modules like #define PetscScalar real8 etc? Seems reasonable also to me. Barry -- next part -- An HTML attachment was scrubbed... URL: http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20080423/28ee5989/attachment.html

removing f77 support from PETSc?

Barry, Since g95 and gfortran seem to work OK now, there are no very compelling reasons to keep f77 support that I know of. It is worth asking, however: 1) How many people use the current F77-style calls in their code? Such a change could be a huge pain for them if they've got lots of these