Re: [petsc-dev] HYPRE_LinSysCore.h
On Tue, Jan 29, 2019 at 5:20 PM Victor Eijkhout via petsc-dev < petsc-dev@mcs.anl.gov> wrote: > > > On Jan 29, 2019, at 3:58 PM, Balay, Satish wrote: > > -args.append('--without-fei') > > > The late-1990s Finite Element Interface? > I would guess FEI is still actively used and interfaces to 1960's FE codes at the labs. > > I’ll enable it and see if anyone complains about it breaking whatever. > > Victor. >
Re: [petsc-dev] HYPRE_LinSysCore.h
On Jan 29, 2019, at 3:58 PM, Balay, Satish mailto:ba...@mcs.anl.gov>> wrote: -args.append('--without-fei') The late-1990s Finite Element Interface? I’ll enable it and see if anyone complains about it breaking whatever. Victor.
Re: [petsc-dev] HYPRE_LinSysCore.h
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
[petsc-dev] HYPRE_LinSysCore.h
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? Victor.