Project

General

Profile

Bug #1015

make install-mdrun broken on release-4.6

Added by Alexey Shvetsov over 6 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Category:
build system
Target version:
Affected version - extra info:
Affected version:
Difficulty:
uncategorized
Close

Description

Make install mdrun broken on release-4.6 target

alexxy@x201 ~/Src/gromacs_build $ LANG=C make install-mdrun 
[  0%] Generating version information
[  0%] Built target gmx_version
[ 80%] Built target gmx
[ 91%] Built target md
[ 95%] Built target gmxpreprocess
[ 98%] Built target mdrun
[100%] Installing mdrun
-- Install configuration: "Release" 
-- Install component: "libraries" 
-- Up-to-date: /tmp/gromacs/lib/libgmx.so.6
-- Up-to-date: /tmp/gromacs/lib/libgmx.so
-- Up-to-date: /tmp/gromacs/lib/libmd.so.6
-- Up-to-date: /tmp/gromacs/lib/libmd.so
-- Up-to-date: /tmp/gromacs/lib/libgmxpreprocess.so.6
-- Up-to-date: /tmp/gromacs/lib/libgmxpreprocess.so
CMake Error at /home/alexxy/Src/gromacs_build/src/tools/cmake_install.cmake:3523 (FILE):
  file INSTALL cannot find
  "/home/alexxy/Src/gromacs_build/src/tools/libgmxana.so.6".
Call Stack (most recent call first):
  /home/alexxy/Src/gromacs_build/src/cmake_install.cmake:52 (INCLUDE)
  /home/alexxy/Src/gromacs_build/cmake_install.cmake:39 (INCLUDE)

make[3]: *** [src/kernel/CMakeFiles/install-mdrun] Error 1
make[2]: *** [src/kernel/CMakeFiles/install-mdrun.dir/all] Error 2
make[1]: *** [src/kernel/CMakeFiles/install-mdrun.dir/rule] Error 2
make: *** [install-mdrun] Error 2

Associated revisions

Revision b64eea39 (diff)
Added by Mark Abraham over 6 years ago

Fixed install-xxx functionality broken in 9628e27d

Only the CPack component definitions needed fixing, inasmuch as they
are what is used for the "make install-xxx" functionality. I separated
"libraries" component into "libraries", "libraries-gmxpreprocess" and
"libraries-gmxana" for, respectively, the core gmx/md/etc. libraries,
and those particular to src/kernel programs and src/tools programs.
Now "make install-xxx" correctly compiles, links and installs only the
required dependencies, and the wrong dependencies introduced in the
above commit are removed.

Fixes #1015

Change-Id: I3e848e69d126305943370d1f294e44d5389e1934

History

#1 Updated by Mark Abraham over 6 years ago

These issues got created when https://gerrit.gromacs.org/#/c/1296/ got merged too soon. I'll be able to contribute to their solution next week.

#2 Updated by Roland Schulz over 6 years ago

  • Status changed from New to Closed

#3 Updated by Suman Chakrabarty about 5 years ago

I am still encountering the same issue in version 4.6.5. "make install-mdrun" produces the following error:

[ 64%] Built target gmx
[ 91%] Built target md
[ 97%] Built target gmxpreprocess
[ 98%] Built target mdrun
Scanning dependencies of target install-mdrun
[100%] Installing mdrun
-- Install configuration: "Release" 
-- Install component: "libraries" 
CMake Error at /home/suman/sources/gromacs-4.6.5/build/src/gmxlib/cmake_install.cmake:44 (FILE):
  file INSTALL cannot find
  "/home/suman/sources/gromacs-4.6.5/build/src/gmxlib/CMakeFiles/CMakeRelink.dir/libgmx.so.8".
Call Stack (most recent call first):
  /home/suman/sources/gromacs-4.6.5/build/src/cmake_install.cmake:49 (INCLUDE)
  /home/suman/sources/gromacs-4.6.5/build/cmake_install.cmake:51 (INCLUDE)

make[3]: *** [src/kernel/CMakeFiles/install-mdrun] Error 1
make[2]: *** [src/kernel/CMakeFiles/install-mdrun.dir/all] Error 2
make[1]: *** [src/kernel/CMakeFiles/install-mdrun.dir/rule] Error 2
make: *** [install-mdrun] Error 2

#4 Updated by Mark Abraham about 5 years ago

  • Description updated (diff)
  • Affected version set to N/A

#5 Updated by Mark Abraham about 5 years ago

Worked fine for me on release-4-6 branch with cmake 2.8.12.2. libgmx is correctly added to the libraries CPack component already in src/gmxlib/CMakeLists.txt, so I don't think there is a problem for GROMACS to solve. I suspect your behaviour might be specific to a CMake version, or perhaps re-configuration of your build directory. If you can reproduce that with a fresh build directory, then perhaps there's an issue to fix.

Also available in: Atom PDF