Closed robertodr closed 4 years ago
These are for the linking order warnings?
These are for the linking order warnings?
Forgot to describe what I did... Yes, these fix those warnings and also disallow CMake from being "too eager" in searching for dependencies.
Merging #300 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #300 +/- ##
=======================================
Coverage 38.60% 38.60%
=======================================
Files 168 168
Lines 11747 11747
=======================================
Hits 4535 4535
Misses 7212 7212
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update a4521ae...29292cd. Read the comment docs.
I still get these warnings...
Was this on a fresh copy with no installations around?
Yes, fresh copy. First install is fine, then
$ touch src/input/mrchem.in
and a new make
gives (without removing the old install)
-- Configuring done
CMake Warning at src/CMakeLists.txt:78 (add_executable):
Cannot generate a safe runtime search path for target mrchem.x because
there is a cycle in the constraint graph:
dir 0 is [/home/stig/src/mrchem-master/build/lib]
dir 1 must precede it due to runtime library [libxcfun.so.2]
dir 1 is [/home/stig/src/mrchem-master/install/lib]
dir 0 must precede it due to runtime library [libmrchem.so]
Some of these libraries may not be found correctly.
Should we still merge this?
I'd merge: they don't solve the problem, but they don't hurt either.
Generated by :no_entry_sign: Danger