dolfin team mailing list archive

[Johannes Ring <694507@xxxxxxxxxxxxxxxxxx>]

I have tried to reproduce this, but without success. What I did was to
let Dorsal build OpenMPI, PETSc, and DOLFIN using the attached platform
file. I did see some similar warnings like

  CMake Warning at demo/la/eigenvalue/cpp/CMakeLists.txt:31 (add_executable):
    Cannot generate a safe linker search path for target demo_eigenvalue
    because files in some directories may conflict with libraries in implicit
    directories:

      link library [libumfpack.so] in /usr/lib may be hidden by files in:
        /work/johannr/dorsal/Work/FEniCS/lib
      link library [libamd.so] in /usr/lib may be hidden by files in:
        /work/johannr/dorsal/Work/FEniCS/lib

    Some of these libraries may not be found correctly.

but nothing related to OpenMPI and PETSc.

Anyway, these are just CMake warnings and, unless you see some strange
behavior, can safely be ignored.

** Attachment added: "test.platform"
   https://bugs.launchpad.net/dolfin/+bug/694507/+attachment/1914446/+files/test.platform

-- 
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.
https://bugs.launchpad.net/bugs/694507

Title:
  Incorrect path for link libraries from PETSc

Status in DOLFIN:
  Confirmed

Bug description:
  The correct path is not being added for some link libraries provided
  by PETSc (specifically, those provided by PCC_LINKER_LIBS).

  I see this when building PETSc and DOLFIN using a locally installed OpenMPI. The consequence is that during configuration I get
  messages like

   Cannot generate a safe runtime search path for target
    dg-advection-diffusion-demo because files in some directories may conflict
    with libraries in implicit directories:

      runtime library [libmpi_f90.so.0] in /usr/lib may be hidden by files in:
        /home/gnw20/local/lib