[petsc-dev] Structure of Elemental changed?

[Balay, Satish]

On Thu, 11 Apr 2019, Victor Eijkhout via petsc-dev wrote:

> 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?

Nothing that I'm aware off..

balay at sb /home/balay/petsc (maint-3.10=)
$ git log v3.10.4..v3.10.5 config/BuildSystem/config/packages/elemental.py
balay at sb /home/balay/petsc (maint-3.10=)
$ git log v3.10.3..v3.10.5 config/BuildSystem/config/packages/elemental.py
commit 34de70d43c4e66e50d45922c722354dfed66f898
Author: Satish Balay <balay at mcs.anl.gov>
Date:   Tue Jan 22 11:43:58 2019 -0600

    Elemental: use update with gcc8 compile fix
balay at sb /home/balay/petsc (maint-3.10=)
$ 

The above change in 3.10.4 is a fix to elemental to compile with gcc8
- but I don't see any change that changed the elemental libraries
built.

And here is the list of elemental libs in one of th linux builds with current 'maint'

[balay at asterix lib]$ ls -lt libEl*
lrwxrwxrwx. 1 petsc petsc        21 Apr  7 13:32 libElSuiteSparse.so -> libElSuiteSparse.so.0
lrwxrwxrwx. 1 petsc petsc        22 Apr  7 13:32 libElSuiteSparse.so.0 -> libElSuiteSparse.so.87
lrwxrwxrwx. 1 petsc petsc        10 Apr  7 13:32 libEl.so -> libEl.so.0
lrwxrwxrwx. 1 petsc petsc        11 Apr  7 13:32 libEl.so.0 -> libEl.so.87
-rwxr-xr-x. 1 petsc petsc 357188856 Apr  7 13:31 libEl.so.87
-rwxr-xr-x. 1 petsc petsc     87712 Apr  7 13:19 libElSuiteSparse.so.87
[balay at asterix lib]$ 

Satish


> 
> 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.
> 
> 
> 
>