Skip to content

Deployed geosx still points to build directory #736

@TotoGaz

Description

@TotoGaz

I compile and install geosx with the python scripts/build-config.py ....
Then I cd to the build directory and perform the make, make install commands.

The deployed geosx executable is indeed linked to the libgeosx_core.so library. But

  • this library is not deployed in the installation directory alongside geosx,
  • geosx points to this library in the build directory.

See :

-bash-4.2$ readelf --dynamic /path/to/bin/geosx 

Dynamic section at offset 0x11ac0 contains 77 entries:
  Tag        Type                         Name/Value
 0x0000000000000001 (NEEDED)             Shared library: [libgeosx_core.so]
 0x0000000000000001 (NEEDED)             Shared library: [libtrilinoscouplings.so.12]
 ... SNIP ... 
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x000000000000001d (RUNPATH)            Library runpath: [/data_local/sw/OpenMPI/RHEL7/3.1.5/gcc/8.3.0/lib:/work206/workrd/DEV/gazzola-GEOSX/sources/GEOSX/build-environment-release/lib:/scratchrd/DEV/j0436735/docker-attempt-pandev14-version/GEOSX_TPL/trilinos/lib:/data_local/sw/OpenMPI/RHEL7/3.1.5/gcc/8.3.0/lib]
 0x000000000000000c (INIT)               0x4093a8
 ... SNIP ...
 0x0000000000000000 (NULL)               0x0

Notice the Library runpath which points to /work206/workrd/DEV/gazzola-GEOSX/sources/GEOSX/build-environment-release/lib, which is part of the build directory.
Also, the installation directory does not contain libgeosx_core.so: only the build folder does.

I can see 2 possibilities

  • Deploy libgeosx_core.so and make geosx use it.
  • Convert libgeosx_core.so to the .a library: it is indeed surprising that all the other libraries are .a files and only libgeosx_core.so is a .so. May this be an inattention mistake?

Any comments?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions