Skip to content

installation of AmberTools v20 is broken due to switch to CMake in custom easyblock for Amber #14021

@boegel

Description

@boegel

In easybuilders/easybuild-easyblocks#2445 we updated the Amber easyblock to use CMake, but we failed to take into account that that same easyblock is also used for AmberTools.

Problems with AmberTools-20-intel-2020a-Python-3.8.2.eb:

  • the runtime patching done on AmberTools/src/cpptraj/configure is failing, because the relative path is now run (building is done from a separate build dir due to the switch to CMakeMake), can be fixed by using %(builddir)s/AmberTools/src/cpptraj/configure (but not sure if that patching is still needed when using CMake)
  • CMake is missing as a build dependency
  • configuring with CMake fails with:
CMake Error at cmake/LibraryTracking.cmake:174 (message):
  Incorrect usage.  At least one LIBRARY should be provided.
Call Stack (most recent call first):
  cmake/MPIConfig.cmake:122 (import_libraries)
  CMakeLists.txt:118 (include)

Easy fix may be to tweak the Amber easyblock a bit more to stick to the old approach for AmberTools?

@branfosj @akesandgren Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions