I can't reproduce with current petsc-dev.
I'll suggest doing a clean build and see if the problem persists. If so
- try running a debugger to get the stack trace [with COPTFLAGS="-g -O2"]
git clean -f -d -x
Satish
On Thu, 12 Dec 2013, Satish Balay wrote:
> Ok - perhaps the attached configure.
Ok - perhaps the attached configure.log didn't correspond to this
build.
Will check with these options and see if I can reproduce.
Satish
On Thu, 12 Dec 2013, John Mousel wrote:
> Satish,
>
> The script that pulled petsc-dev uses:
>
> export PETSC_DIR=/home/augspurger/NumericalLibraries/petsc
Satish,
The script that pulled petsc-dev uses:
export PETSC_DIR=/home/augspurger/NumericalLibraries/petsc
git clone https://bitbucket.org/petsc/petsc
cd petsc
export PETSC_ARCH=gnu-opt
./config/configure.py --with-cc=gcc --with-cxx=g++ --with-fc=gfortran
--download-openmpi --download-metis --down
[posting compressed logs would bypass the moderation on this list. Or
one can send logs to petsc-maint]
TEST configureInstallationMethod from
PETSc.utilities.petscdir(/home/jmousel/NumericalLibraries/petsc-hg/petsc-d
