Each time - do you see binary chars at the end of configure.log - after the _access test?
I don't know why this would happen. Perhaps you can try with the same configure options - and send in the configure.log [petsc-maint at mcs.anl.gov] for us to comapre. Satish On Wed, 21 Jan 2009, Matt Funk wrote: > I tried it multiple from a fresh tarball each time. Same thing everytime. > Did you mean try with different configure options? If so, which ones did you > have in mind? > > thanks > matt > > > > On Wednesday 21 January 2009, Satish Balay wrote: > > Not sure what the issue is. I see the configure.log [from the rejected > > e-mail] - there are some binary chars at the end of the file. > > > > Perhaps you can retry and see? [after rm *.log]. If you still have > > issues - send configure.log to petsc-maint at mcs.anl.gov > > > > Satish > > > > On Wed, 21 Jan 2009, Matt Funk wrote: > > > Hi, > > > > > > i was wondering if there is any issues with compiling petsc based on > > > mvapich-0.9.9. I tells me that it is unable to configure with given > > > options. I configure as such: > > > ./config/configure.py > > > --with-mpi-include=/usr/mpi/mvapich-0.9.9/gcc/include > > > --with-mpi-lib=/usr/mpi/mvapich-0.9.9/gcc/lib/libmpich.a > > > --with-debugging=0 --with-log=0 --with-cc=gcc --with-fc=gfortran > > > --download-f-blas-lapack=1 --download-superlu=1 --download-superlu_dist=1 > > > --download-spooles=1 --download-hypre=hypre-2.4.0b.tar.gz > > > > > > I can compile ?petsc against the mvapich2 libraries just fine. > > > > > > > > > thanks > > > matt > > >
