This is coming from mumps. PETSc configure option --with-debugging=0 does not control it.
You might have to check which mumps option controls it - and perhaps use the runtime option -mat_mumps_icntl_(x) Satish On Sun, 19 Apr 2020, san.tempo...@gmail.com wrote: > I have just successfully compiled PETSc with > > ./configure --with-cc=mpicc --with-fc=mpif90 -with-cxx=mpicxx > --prefix=/home/santiago/usr/local --with-make-np=10 > --with-shared-libraries > --with-packages-download-dir=/home/santiago/Documents/installers/petsc > --download-fblaslapack --download-mumps --download-scalapack > --with-debugging=0 COPTFLAGS='-O -O3 -march=native -mtune=native' > FOPTFLAGS='-O -O3 -march=native -mtune=native' CXXOPTFLAGS='-O -O3 > -march=native -mtune=native' > > When I run my program, I get very large amounts of information from mumps. > For example, the first such block starts with > > Entering DMUMPS 5.2.1 from C interface with JOB, N = 1 15 > executing #MPI = 8, without OMP > > ================================================= > This MUMPS version includes code for SAVE_RESTORE > ================================================= > L U Solver for unsymmetric matrices > Type of parallelism: Working host > > ****** ANALYSIS STEP ******** > > ** Max-trans not allowed because matrix is distributed > > Entering analysis phase with ... > > Is there a way to control (and eliminate) that output? > I guessed with --with-debugging=0 would do the trick, but that was not the > case. > > Thanks, > Santiago >