On Wed, 23 Apr 2008, Satish Balay wrote: > On Wed, 23 Apr 2008, Amit.Itagi at seagate.com wrote: > > > Using configure Options: --PETSC_ARCH=linux-gnu-c-debug > > --with-scalar-type=complex --with-debugging=yes --with-clanguage=cxx > > --with-mpi=1 --download-mpich=1 --with-metis=1 --download-metis=1 > > --with-parmetis=1 --download-parmetis=1 --with-superlu_dist=1 > > --download-superlu_dist=1 --with-mumps=1 --download-blacs=1 > > --download-scalapack=1 --download-mumps=1 COPTFLAGS="-O3 -march=p4 > > -mtune=p4 -ffast-math -malign-double -funroll-loops -pipe > > -fomit-frame-pointer -finline-functions -msse2" CXXOPTFLAGS="-O3 > > -march=p4 -mtune=p4 -ffast-math -malign-double -funroll-loops -pipe > > -fomit-frame-pointer -finline-functions -msse2" --with-shared=0 > > > For one - when debugging - you should not use optimization flags "-O3 etc.." > > Can you send the corresponding configure.log to petsc-maint at mcs.anl.gov? > > Also - what do you have for 'hg status'
Ah - I think you pulled petsc-dev - but not BuildSystem. If you are using petsc-dev - you should be pulling both. http://www-unix.mcs.anl.gov/petsc/petsc-as/developers/index.html Satish
