[petsc-dev] Structure of Elemental changed?

[Victor Eijkhout]

This rpm was make with 3.10.3:

root at build-BLDCHROOT:SPECS # rpm -qlp ../RPMS/x86_64/tacc-petsc-intel18-impi18_0-package-3.10-4.el7.x86_64.rpm  | grep libElSuite
/home1/apps/intel18/impi18_0/petsc/3.10/skylake-debug/lib/libElSuiteSparse.so
/home1/apps/intel18/impi18_0/petsc/3.10/skylake-debug/lib/libElSuiteSparse.so.0
/home1/apps/intel18/impi18_0/petsc/3.10/skylake-debug/lib/libElSuiteSparse.so.87

This with (as best I can tell) 3.10.4:

root at build-BLDCHROOT:SPECS # rpm -qlp ../RPMS/x86_64/tacc-petsc-intel18-impi18_0-package-3.10-5.el7.x86_64.rpm  | grep libElSuite
/home1/apps/intel18/impi18_0/petsc/3.10/skylake-debug/lib/libElSuiteSparse.so

Did something change in Elemental that it now generates only one library?

I think I now need to rebuild libmesh, because it seems to “know” that there is an .so.0 file.

Can I suggest that you limit such changes in libraries to minor version updates, and not point updates? I’m sort of working on the assumption that for our users I can install something as “petsc/3.10” and it keeps working for them if I make a point update in the installation.

Victor.