libmesh-users

[Libmesh-users] make check Error: Solver is unknown.

[<ed...@op...>]

Hello,

I am getting an error with `make check`. I can live with another 
compilation that I already have, but if you want the debugging 
information, let me know.


** Compilation set-up of PETSc and libmesh

My compilation configuration can be seen here:

- PETSc:
   - https://notabug.org/broncodev/petsc-pkgbuild
     - commit ed0b0b66dc38da1a2b68be1185ad557d1201c5e6
   - main script: 
https://notabug.org/broncodev/petsc-pkgbuild/src/ed0b0b66dc38da1a2b68be1185ad557d1201c5e6/PKGBUILD
   - extra dependencies: 
https://notabug.org/broncodev/petsc-pkgbuild/src/ed0b0b66dc38da1a2b68be1185ad557d1201c5e6/test_optdepends.sh

   - This results in the following `configure` flags:
     #+begin_EXAMPLE
       LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now 
--prefix=/usr/petsc/linux-c-opt --CXXOPTFLAGS=-O3 --CFLAGS=-fPIC 
-fopenmp -O3 -march=x86-64 -mtune=generic --CXXFLAGS=-fPIC -fopenmp -O3 
-march=x86-64 -mtune=generic --FFLAGS=-fPIC -fopenmp -O3 -march=x86-64 
-mtune=generic --FCFLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic 
--F90FLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic 
--F77FLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic 
--with-cxx-dialect=C++11 --with-fftw=1 --with-hdf5=1 --with-mpi=1 
--with-pic=1 --with-shared-libraries=1 --with-zlib=1 
--with-scalar-type=complex --with-hypre=1 --with-mumps=1 --with-fftw=1 
--with-hdf5=1 --with-scalapack=1 --with-suitesparse=1 --with-metis=1 
--with-parmetis=1 --with-ptscotch=1 
--with-ptscotch-lib="[libesmumps.so,libptscotch.so,libptscotcherr.so,libscotch.so,libscotcherr.so,libbz2.so]" 
--with-ptscotch-include=/usr/include/scotch --with-superlu=1 
--with-superlu-lib=-lsuperlu --with-superlu-include=/usr/include/superlu 
--with-eigen=1 --with-eigen-include=/usr/include/eigen3 --with-openmp=1 
--with-hwloc=1 --with-hwloc-pkg-config=/usr/lib/pkgconfig/ --with-cgns=1 
--with-png=1 --with-png-pkg-config=/usr/lib/pkgconfig/ --with-med=1
     #+end_EXAMPLE


- libmesh: https://notabug.org/broncodev/libmesh-pkgbuild
   - commit 4286225389795cdacec80b1af669f03c2edabb43
   - main script: 
https://notabug.org/broncodev/libmesh-pkgbuild/src/4286225389795cdacec80b1af669f03c2edabb43/PKGBUILD
   - This results in the following `configure` flags:
     #+begin_EXAMPLE
       configure: running /bin/sh ./configure --disable-option-checking 
'--prefix=/usr'  '--enable-petsc-hypre-required' '--with-metis=PETSc' 
'--enable-metaphysicl-required' '--enable-vtk-required' '--enable-curl' 
'--enable-hdf5' '--enable-complex' '--with-pic' '--enable-mpi' 
'--enable-fftw' '--enable-shared' '--enable-unique-id' '--enable-march' 
'--enable-ifem' '--enable-nodeconstraint' 'CXXFLAGS=-fPIC -fopenmp -O3 
-march=x86-64 -mtune=generic' 
'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now' 
'CPPFLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic 
-D_FORTIFY_SOURCE=2' 'CFLAGS=-fPIC -fopenmp -O3 -march=x86-64 
-mtune=generic' 'FCFLAGS=-fPIC -fopenmp -O3 -march=x86-64 
-mtune=generic' 'FFLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic' 
'METHODS=opt oprof dbg' 'PETSC_DIR=/usr/petsc/linux-c-opt' 
'--enable-dap' '--disable-testsets' 'CXX=mpicxx' 'CC=mpicc' 'F77=mpif77' 
'FC=mpif90' 'CPPFLAGS= -fPIC -fopenmp -O3 -march=x86-64 -mtune=generic 
-D_FORTIFY_SOURCE=2' 'LIBS=-L/lib -lhdf5 -Wl,-rpath,/lib -ldl ' 
--cache-file=/dev/null --srcdir=.
     #+end_EXAMPLE


** The error is this:

#+begin_EXAMPLE
   make  check-TESTS
   make[4]: Entering directory 
'/folder/libmesh/examples/reduced_basis/reduced_basis_ex7'
   ,***************************************************************
   ,* Running Example reduced_basis_ex7:
   ,*   ./example-dbg -online_mode 0 -ksp_type preonly -pc_type lu 
-pc_factor_mat_solver_type mumps
   ,***************************************************************

   Error: Solver  is unknown.
   WARNING! There are options you set that were not used!
   WARNING! could be spelling mistake, etc!
   There are 4 unused database options. They are:
   Option left: name:-ksp_type value: preonly
   Option left: name:-online_mode value: 0
   Option left: name:-pc_factor_mat_solver_type value: mumps
   Option left: name:-pc_type value: lu

    
----------------------------------------------------------------------------
   | Reference count information                                          
       |
    
----------------------------------------------------------------------------
   | N7libMesh4ElemE reference count information:
   |  Creations:    1
   |  Destructions: 1
   | N7libMesh9DofObjectE reference count information:
   |  Creations:    1
   |  Destructions: 1
    
----------------------------------------------------------------------------
   FAIL: run.sh
   ====================================================
   1 of 1 test failed
   Please report to lib...@li...
   ====================================================
   make[4]: *** [Makefile:1009: check-TESTS] Error 1
   make[4]: Leaving directory 
'/folder/libmesh/examples/reduced_basis/reduced_basis_ex7'
   make[3]: *** [Makefile:1136: check-am] Error 2
   make[3]: Leaving directory 
'/folder/libmesh/examples/reduced_basis/reduced_basis_ex7'
   make[2]: *** [Makefile:1138: check] Error 2
   make[2]: Leaving directory 
'/folder/libmesh/examples/reduced_basis/reduced_basis_ex7'
   make[1]: *** [Makefile:727: check-recursive] Error 1
   make[1]: Leaving directory '/folder/libmesh/examples'
   make: *** [Makefile:31749: check-recursive] Error 1
#+end_EXAMPLE

If you need more information, please, let me know

-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vf...
 
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  

Re: [Libmesh-users] make check Error: Solver is unknown.

[John P. <jwp...@gm...>]

On Sat, Dec 21, 2019 at 3:42 PM <ed...@op...> wrote:

> Hello,
>
> I am getting an error with `make check`. I can live with another
> compilation that I already have, but if you want the debugging
> information, let me know.
>
>
> ** Compilation set-up of PETSc and libmesh
>
> My compilation configuration can be seen here:
>
> - PETSc:
>    - https://notabug.org/broncodev/petsc-pkgbuild
>      - commit ed0b0b66dc38da1a2b68be1185ad557d1201c5e6
>    - main script:
>
> https://notabug.org/broncodev/petsc-pkgbuild/src/ed0b0b66dc38da1a2b68be1185ad557d1201c5e6/PKGBUILD
>    - extra dependencies:
>
> https://notabug.org/broncodev/petsc-pkgbuild/src/ed0b0b66dc38da1a2b68be1185ad557d1201c5e6/test_optdepends.sh
>
>    - This results in the following `configure` flags:
>      #+begin_EXAMPLE
>        LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now
> --prefix=/usr/petsc/linux-c-opt --CXXOPTFLAGS=-O3 --CFLAGS=-fPIC
> -fopenmp -O3 -march=x86-64 -mtune=generic --CXXFLAGS=-fPIC -fopenmp -O3
> -march=x86-64 -mtune=generic --FFLAGS=-fPIC -fopenmp -O3 -march=x86-64
> -mtune=generic --FCFLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic
> --F90FLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic
> --F77FLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic
> --with-cxx-dialect=C++11 --with-fftw=1 --with-hdf5=1 --with-mpi=1
> --with-pic=1 --with-shared-libraries=1 --with-zlib=1
> --with-scalar-type=complex --with-hypre=1 --with-mumps=1 --with-fftw=1
> --with-hdf5=1 --with-scalapack=1 --with-suitesparse=1 --with-metis=1
> --with-parmetis=1 --with-ptscotch=1
> --with-ptscotch-lib="[libesmumps.so,libptscotch.so,libptscotcherr.so,libscotch.so,libscotcherr.so,libbz2.so]"
>
> --with-ptscotch-include=/usr/include/scotch --with-superlu=1
> --with-superlu-lib=-lsuperlu --with-superlu-include=/usr/include/superlu
> --with-eigen=1 --with-eigen-include=/usr/include/eigen3 --with-openmp=1
> --with-hwloc=1 --with-hwloc-pkg-config=/usr/lib/pkgconfig/ --with-cgns=1
> --with-png=1 --with-png-pkg-config=/usr/lib/pkgconfig/ --with-med=1
>      #+end_EXAMPLE
>
>
> - libmesh: https://notabug.org/broncodev/libmesh-pkgbuild
>    - commit 4286225389795cdacec80b1af669f03c2edabb43
>    - main script:
>
> https://notabug.org/broncodev/libmesh-pkgbuild/src/4286225389795cdacec80b1af669f03c2edabb43/PKGBUILD
>    - This results in the following `configure` flags:
>      #+begin_EXAMPLE
>        configure: running /bin/sh ./configure --disable-option-checking
> '--prefix=/usr'  '--enable-petsc-hypre-required' '--with-metis=PETSc'
> '--enable-metaphysicl-required' '--enable-vtk-required' '--enable-curl'
> '--enable-hdf5' '--enable-complex' '--with-pic' '--enable-mpi'
> '--enable-fftw' '--enable-shared' '--enable-unique-id' '--enable-march'
> '--enable-ifem' '--enable-nodeconstraint' 'CXXFLAGS=-fPIC -fopenmp -O3
> -march=x86-64 -mtune=generic'
> 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now'
> 'CPPFLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic
> -D_FORTIFY_SOURCE=2' 'CFLAGS=-fPIC -fopenmp -O3 -march=x86-64
> -mtune=generic' 'FCFLAGS=-fPIC -fopenmp -O3 -march=x86-64
> -mtune=generic' 'FFLAGS=-fPIC -fopenmp -O3 -march=x86-64 -mtune=generic'
> 'METHODS=opt oprof dbg' 'PETSC_DIR=/usr/petsc/linux-c-opt'
> '--enable-dap' '--disable-testsets' 'CXX=mpicxx' 'CC=mpicc' 'F77=mpif77'
> 'FC=mpif90' 'CPPFLAGS= -fPIC -fopenmp -O3 -march=x86-64 -mtune=generic
> -D_FORTIFY_SOURCE=2' 'LIBS=-L/lib -lhdf5 -Wl,-rpath,/lib -ldl '
> --cache-file=/dev/null --srcdir=.
>      #+end_EXAMPLE
>
>
> ** The error is this:
>
> #+begin_EXAMPLE
>    make  check-TESTS
>    make[4]: Entering directory
> '/folder/libmesh/examples/reduced_basis/reduced_basis_ex7'
>    ,***************************************************************
>    ,* Running Example reduced_basis_ex7:
>    ,*   ./example-dbg -online_mode 0 -ksp_type preonly -pc_type lu
> -pc_factor_mat_solver_type mumps
>    ,***************************************************************
>
>    Error: Solver  is unknown.
>    WARNING! There are options you set that were not used!
>    WARNING! could be spelling mistake, etc!
>    There are 4 unused database options. They are:
>    Option left: name:-ksp_type value: preonly
>    Option left: name:-online_mode value: 0
>    Option left: name:-pc_factor_mat_solver_type value: mumps
>    Option left: name:-pc_type value: lu


Hmm... it seems to me that you should not hit exactly this error because of
this logic:

  // check that we have the required solver:
  std::string solver;
  solver = input.next(solver);
  if (solver == "mumps")
  {
#ifndef LIBMESH_PETSC_HAVE_MUMPS
    libmesh_example_requires(false, "PETSc compiled with MUMPS support");
#endif
  }
  else if (solver == "superlu")
  {
#ifndef LIBMESH_PETSC_HAVE_SUPERLU_DIST
    libmesh_example_requires(false, "PETSc compiled with SuperLU support");
#endif
  }
  else
  {
     libMesh::err << "Error: Solver " << solver << " is unknown."
                  << std::endl;
     return 1;
  }

i.e. you should hit the "libmesh_example_requires" in the first if-block.
But perhaps you are using an older version of libmesh which doesn't have
this check.

Either way, it's not fatal error with your libmesh build, just an example
that requires a specific solver that you don't have in your build of PETSc.

-- 
John

Re: [Libmesh-users] make check Error: Solver is unknown.

[<ed...@op...>]

> Hmm... it seems to me that you should not hit exactly this error 
> because of
> this logic:
> 
>   // check that we have the required solver:
>   std::string solver;
>   solver = input.next(solver);
>   if (solver == "mumps")
>   {
> #ifndef LIBMESH_PETSC_HAVE_MUMPS
>     libmesh_example_requires(false, "PETSc compiled with MUMPS 
> support");
> #endif
>   }
>   else if (solver == "superlu")
>   {
> #ifndef LIBMESH_PETSC_HAVE_SUPERLU_DIST
>     libmesh_example_requires(false, "PETSc compiled with SuperLU 
> support");
> #endif
>   }
>   else
>   {
>      libMesh::err << "Error: Solver " << solver << " is unknown."
>                   << std::endl;
>      return 1;
>   }
> 
> i.e. you should hit the "libmesh_example_requires" in the first 
> if-block.
> But perhaps you are using an older version of libmesh which doesn't 
> have
> this check.
> 
> Either way, it's not fatal error with your libmesh build, just an 
> example
> that requires a specific solver that you don't have in your build of 
> PETSc.

Thank you for your answer, John. I am using v1.5.1 (as suggested on 
another e-mail). How do I set flags to configure with MUMPS? Does  
--enable-mumps  work? Thank you! Have nice holidays :) .

-------------------------------------------------
This free account was provided by VFEmail.net - report spam to ab...@vf...
 
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!