Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cycle in constraints graph #130

Closed
andlaus opened this issue Jun 4, 2016 · 6 comments
Closed

cycle in constraints graph #130

andlaus opened this issue Jun 4, 2016 · 6 comments

Comments

@andlaus
Copy link
Contributor

andlaus commented Jun 4, 2016

recently cmake started to spit the following warning at me:

CMake Warning at /home/and/src/opm-common/cmake/Modules/OpmSatellites.cmake:295 (add_executable):
  Cannot generate a safe runtime search path for target tutorial1 because
  there is a cycle in the constraint graph:

    dir 0 is [/home/and/src/opm-common/lib]
    dir 1 is [/home/and/src/opm-material/lib]
    dir 2 is [/home/and/src/opm-grid/lib]
    dir 3 is [/home/and/src/ert/install/lib/x86_64-linux-gnu]
      dir 5 must precede it due to runtime library [libecl.so.2]
    dir 4 is [/home/and/tmp/boost-clang-install/lib]
    dir 5 is [/home/and/src/ert/build/lib/x86_64-linux-gnu]
      dir 3 must precede it due to runtime library [libecl.so.2]
    dir 6 is [/usr/lib/openmpi/lib]

  Some of these libraries may not be found correctly.
Call Stack (most recent call first):
  CMakeLists.txt:297 (opm_add_test)

without going into it too deeply, this looks like a problem caused by sibling builds. (maybe FindERT.cmake detects an installed version of the library as well as a sibling one?) also, this may or not be due to the fact that I compiled using ERT using GCC 5.2.1 while I used clang 3.6.2 for Dune and OPM. (given that ERT is plain-C, I consider this being the culprit somewhat unlikely.)

@atgeirr
Copy link
Member

atgeirr commented Jun 6, 2016

What should I do to reproduce?

@andlaus
Copy link
Contributor Author

andlaus commented Jun 6, 2016

I have not too much of an idea since I have not looked into this deeply. In retrospect, I noticed that I accidentially switched between clang and gcc for some modules, but I guess that there is an independent bug somewhere: if ERT's installation directory is specified via ERT_ROOT and happens to be in a sibling directory (in my case ~/src/ert/install), it should not add the library path twice, right?

@atgeirr
Copy link
Member

atgeirr commented Jun 6, 2016

it should not add the library path twice, right?

Should not, but I cannot claim with certainty it doesn't (I use a make installed ert).

@andlaus
Copy link
Contributor Author

andlaus commented Jun 6, 2016

(I use a make installed ert).

Me too, but my install prefix is a sibling of the build and the devel directories...

@atgeirr atgeirr added this to the Release 2016.10 milestone Oct 14, 2016
@atgeirr
Copy link
Member

atgeirr commented Oct 14, 2016

Is this still happening?

@andlaus
Copy link
Contributor Author

andlaus commented Nov 8, 2016

at least not to me ;) closing

@andlaus andlaus closed this as completed Nov 8, 2016
akva2 pushed a commit to akva2/opm-common that referenced this issue Jun 10, 2022
Silence unused argument warnings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants