How come we don't have version checks as a matter of course for
config/packages/xxx.py we constantly get email from people using the wrong
version of external packages with obscure error messages wasting their time and
hours. Better that hypre.py (and others) compare the version number and
Thank you.
Unfortunately, we still have old Hypre-2.11.2 available on EPEL7
repositories.
On 02/08/2018 18:50, Satish Balay wrote:
> https://bitbucket.org/petsc/petsc/commits/e6de09342ce9c4562cc062ff2c1bac4bd956bda0
>
> It is compatible with Hypre-2.14. For Hypre-2.11 - you would have to revert
https://bitbucket.org/petsc/petsc/commits/e6de09342ce9c4562cc062ff2c1bac4bd956bda0
It is compatible with Hypre-2.14. For Hypre-2.11 - you would have to revert the
above change.
Satish
On Thu, 2 Aug 2018, Antonio Trande wrote:
> Hi all.
>
> Petsc-3.9.3 does not compile against Hypre-2.11.2:
>
Hi all.
Petsc-3.9.3 does not compile against Hypre-2.11.2:
mpicc -c -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
-m64 -mtune=generic -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-stro
