You'll have to follow instructions in the 'Project Files' section at http://www-unix.mcs.anl.gov/petsc/petsc-as/documentation/installation.html
[specifically - perhaps that MPI include/library paths in the project files were not updated to point to mpiuni stuff [as would be visible when a PETSc example is compiled from cygwin bash using make.] Satish On Fri, 24 Nov 2006, Matthew Knepley wrote: > We are not able to generate MSDev files, so you will have to alter them > yourself. You need to take out the references to MPI. > > Matt > > On 11/24/06, Ben Tay <zonexo at gmail.com> wrote: > > Hi, > > > > yes I did that. There is no problem if I run the example in cygwin. However, > > if I use the project files for MSDev given in the petsc package, it gives me > > errors during linking. Compiling works though. > > > > I tried to recompile the whole Petsc with mpich1 and there is no such > > errors. > > > > Thank you. > > > > > > > > On 11/25/06, Matthew Knepley <knepley at gmail.com> wrote: > > > You need to configure using --wih-mpi=0. > > > > > > Matt > > > > > > On 11/24/06, Ben Tay < zonexo at gmail.com> wrote: > > > > Hi, > > > > > > > > I've managed to compile and run the examples in MSDev when i use MPICH. > > > > However, if I compile without MPI, I 'll get errors during linking. How > > > > should I modify my configuration file in MSDev so that I can run without > > > > mpi? > > > > > > > > Thank you very much! > > > > > > > > > -- > > > "Failure has a thousand explanations. Success doesn't need one" -- Sir > > > Alec Guiness > > > > > > > > > > > > >
