On Thu, Feb 15, 2024 at 9:27 AM Christoph Junghans <
jung...@votca.org> wrote:
>
> On Thu, Feb 15, 2024 at 9:10 AM Christoph Junghans <
jung...@votca.org> wrote:
> >
> > On Wed, Feb 14, 2024 at 5:20 PM Roozbeh R <
rooz...@gmail.com> wrote:
> > >
> > > Hi Christoph,
> > > thank you for the reply.
> > > docker does not work either as i have already tested it for other packages on my system too without success after lots of trials, so i rather not go after it again.
> > >
> > > Re. your question on the failure of Spack , yes it succeeds in installing the dependencies but fails when building VOTCA itself and there is no error message. it just took a long a long time showing "building votca" before it says: KILLED! (tested two times)
> > Can you do a spack install --verbose ... to see what went on just
> > before it's aborting.
> >
> > >
> > > As for the standard method of installing VOTCA, (cmake -B builddir -S votca -DCMAKE_INSTALL_PREFIX=${prefix} -DINSTALL_CSGAPPS=ON -DUSE_CUDA=ON) , i managed to modify libgromacs.cmake to get read of its earlier complain of not being able to find gmx bin, so now it obviously is possible for cmake to find the location of gmx executable binary, but now after i run cmake i get a new error message:
> > >
> > > "
> > > ...
> > > Found Threads: TRUE
> > > -- Found GROMACS: 2019.6
> > > CMake Error at CMakeLists.txt:136 (message):
> > > Gromacs library was found, but its headers were not. Make sure you have
> > > installed the gromacs-devel package or built gromacs with
> > > -DGMX_INSTALL_LEGACY_API=ON"
> > >
> > > but as i checked DGMX_INSTALL_LEGACY_API=ON option is not supported by gromacsv2019.6 (which is the last gromacs version supporting tabulated potentials) so this option is not applicable and also i compiled my gromacsv2019.6 manually with -DGMXAPI=ON and -DBUILD_SHARED_LIBS=ON which shall suffice. and i don know what gromacs-devel package even is?!
> >
> > CMake is just checking with gmx's version.h exists, see
> >
https://github.com/votca/votca/blob/master/CMakeLists.txt#L133
> > Considering you had to modifiy your libgromacs.cmake to find the gmx
> > binary that hints toward an issue in your installation, but let me do
> > a build against gmx-2019.6 myself. (We usually use the "release-2019"
> > branch, which should be the same v2019.6).