On Tue, 29 Jan 2019, Victor Eijkhout via petsc-dev wrote:
> I’ve been happily freeloading on the petsc installation in the sense that I
> claim to install things like hypre on our clusters by pointing into the petsc
> installation.
>
> Until of course someone needs a bit that does not get installed by petsc.
>
> In this case: HYPRE_LinSysCore.h
>
> Does the petsc hypre installation pick and choose what parts of hypre to
> install? Can I exert some influence on this?
You can get this file with:
diff --git a/config/BuildSystem/config/packages/hypre.py
b/config/BuildSystem/config/packages/hypre.py
index 620e51602a..c3cbd55877 100644
--- a/config/BuildSystem/config/packages/hypre.py
+++ b/config/BuildSystem/config/packages/hypre.py
@@ -68,7 +68,7 @@ class Configure(config.package.GNUPackage):
args.append('--with-fmangle-lapack='+mang)
args.append('--without-mli')
- args.append('--without-fei')
+ #args.append('--without-fei')
args.append('--without-superlu')
if self.getDefaultIndexSize() == 64:
args.append('--enable-bigint')
I don't remember why these hypre modules are disabled by default. They must
have caused grief at some point.
Satish
