Hi,
When something using `make` fails with something like your "Error 2" the
actual error is way earlier in the log as the whole tail is Make
propagating the error state up through the invocations. The path
fragment you mention is indeed from truncation, the "first 300 chars"
thing is mostly to give you bit of context to what's wrong, you need to
look at the actual logged information to see what's up.
Is that CUDA_SDK_ROOT_DIR really supposed to point into that part of the
CUDA SDK tree as you cite it?
Please note that there's an open pull request currently for exactly the
version you're trying to build, I've built it successfully on my system
with a development EasyBuild installation.
https://github.com/easybuilders/easybuild-easyconfigs/pull/9620
// Lars
On 2020-03-11 15:28, Loris Bennett wrote:
Hi,
I'm trying to build a GPU-enabled version of OpenMM. Starting with
OpenMM-7.4.1-foss-2019b-Python-3.7.4
(which built fine) I changed the toolchain to 'fosscuda' and added
configopts = "-DOPENMM_BUILD_CUDA_LIB=ON
-DCUDA_SDK_ROOT_DIR=$CUDA_HOME/extras/CUPTI/samples"
The build then fails with:
[ 57%] Built target OpenMMCUDA
make[1]: Leaving directory
`/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/easybuild_obj'
make: *** [all] Error 2
(at
easybuild/software/EasyBuild/4.1.1/lib/python2.7/site-packages/easybuild/tools/run.py:529
in parse_cmd_output)
== 2020-03-11 10:50:31,848 easyblock.py:3109 WARNING build failed (first 300 chars):
cmd " make -j 20 " exited with exit code 2 and output:
/trinity/shared/easybuild/software/CMake/3.15.3-GCCcore-8.3.0/bin/cmake
-S/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/openmm-7.4.1
-B/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/easybuild_
== 2020-03-11 10:50:31,848 easyblock.py:295 INFO Closing log for application
name OpenMM version 7.4.1
== 2020-03-11 10:50:31,849 build_log.py:265 INFO FAILED: Installation ended
unsuccessfully (build directory:
/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4): build failed
(first 300 chars): cmd " make -j 20 " exited with exit code 2 and output:
/trinity/shared/easybuild/software/CMake/3.15.3-GCCcore-8.3.0/bin/cmake
-S/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/openmm-7.4.1
-B/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/easybuild_
(took 2 min 16 sec)
== 2020-03-11 10:50:31,849 build_log.py:265 INFO Results of the build can be
found in the log file(s)
/tmp/eb-KFw1Uj/easybuild-OpenMM-7.4.1-20200311.104815.vsMFt.log
== 2020-03-11 10:50:31,850 build_log.py:169 ERROR EasyBuild crashed with an error (at
easybuild/software/EasyBuild/4.1.1/lib/python2.7/site-packages/easybuild/base/exceptions.py:124
in __init__): build failed (first 300 chars): cmd " make -j 20 " exited with
exit code 2 and output:
/trinity/shared/easybuild/software/CMake/3.15.3-GCCcore-8.3.0/bin/cmake
-S/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/openmm-7.4.1
-B/trinity/shared/easybuild/build/OpenMM/7.4.1/fosscuda-2019b-Python-3.7.4/easybuild_
(at
easybuild/software/EasyBuild/4.1.1/lib/python2.7/site-packages/easybuild/main.py:116
in build_and_install_software)
Is the reference to
easybuild_
real and therefore something to do with the actual error, or has the
path just fallen victim to some form of truncation?
Either way, does anyone have an idea about what the problem is?
Cheers,
Loris
