[petsc-dev] control configure summary output

Satish Balay balay at mcs.anl.gov
Thu Jan 28 17:43:06 CST 2010


Matt,

currently configure dumps the following to the screen

-------------------------------------------------
Compilers:
  C Compiler:         /home/balay/soft/linux64/mpich2-1.1/bin/mpicc  -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3 
  Fortran Compiler:   /home/balay/soft/linux64/mpich2-1.1/bin/mpif90  -fPIC -Wall -Wno-unused-variable -g  
Linkers:
  Shared linker:   /home/balay/soft/linux64/mpich2-1.1/bin/mpicc  -shared  -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3 
  Dynamic linker:   /home/balay/soft/linux64/mpich2-1.1/bin/mpicc  -shared  -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3 
PETSc:
  **
  ** Before running "make" your PETSC_ARCH must be specified with:
  **  ** setenv PETSC_ARCH asterix-foo (csh/tcsh)
  **  ** PETSC_ARCH=asterix-foo; export PETSC_ARCH (sh/bash)
  **
  **
  ** Before running "make" your PETSC_DIR must be specified with:
  **  ** setenv PETSC_DIR /home/balay/tmp/petsc-dev (csh/tcsh)
  **  ** PETSC_DIR=/home/balay/tmp/petsc-dev; export PETSC_DIR (sh/bash)
  **
  **
  ** Now build the libraries with "make all"
  **
  Clanguage: C
  Scalar type: real
MPI:
  Includes: -I/home/balay/soft/linux64/mpich2-1.1/include
X11:
  Includes: 
  Library:  -lX11
  PETSc shared libraries: enabled
  PETSc dynamic libraries: disabled
  Memory alignment:16
BLAS/LAPACK: -llapack -lblas
-------------------------------------------------

Its a bit wildy - and some of the recommendations get missed out. I'd like to to read something like:

-------------------------------------------------
Compilers:
  C Compiler:         /home/balay/soft/linux64/mpich2-1.1/bin/mpicc  -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3 
  Fortran Compiler:   /home/balay/soft/linux64/mpich2-1.1/bin/mpif90  -fPIC -Wall -Wno-unused-variable -g  
Linkers:
  Shared linker:   /home/balay/soft/linux64/mpich2-1.1/bin/mpicc  -shared  -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3 
  Dynamic linker:   /home/balay/soft/linux64/mpich2-1.1/bin/mpicc  -shared  -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3 
PETSc:
  PETSC_DIR: /home/balay/tmp/petsc-dev
  PETSC_ARCH: asterix-foo        
  Clanguage: C
  Scalar type: real
  PETSc shared libraries: enabled
  PETSc dynamic libraries: disabled
  Memory alignment:16
MPI:
  Includes: -I/home/balay/soft/linux64/mpich2-1.1/include
X11:
  Includes: 
  Library:  -lX11
BLAS/LAPACK: -llapack -lblas
  ** *************************************************************
  ** Before running "make" your PETSC_ARCH must be specified with:
  **  ** setenv PETSC_ARCH asterix-foo (csh/tcsh)
  **  ** PETSC_ARCH=asterix-foo; export PETSC_ARCH (sh/bash)
  **
  **
  ** Before running "make" your PETSC_DIR must be specified with:
  **  ** setenv PETSC_DIR /home/balay/tmp/petsc-dev (csh/tcsh)
  **  ** PETSC_DIR=/home/balay/tmp/petsc-dev; export PETSC_DIR (sh/bash)
  **
  **
  ** Now build the libraries with "make all"
  ** *************************************************************
-------------------------------------------------

Or simplify the last section to:

  ** *************************************************************
  ** Now build the libraries with "make PETSC_ARCH=asterix-foo PETSC_DIR=/home/balay/tmp/petsc-dev all"
  ** *************************************************************

Is there a way to control the order in which this stuff is dumped to
the screen [from the various .py files - so that it goes into the same
'PETSc:' section?]

thanks,
satish



More information about the petsc-dev mailing list