-
Notifications
You must be signed in to change notification settings - Fork 24
GROMACS File Readers #543
Comments
I'm wondering if all the gmx files now need a refactor. |
Any details? |
I had an old version of a gromacs libarray around, which caused those errors. Everything is fine now, it was a user error. |
We might need to update cmake, Found GROMACS: /usr/lib/x86_64-linux-gnu/libgromacs_d.so (found suitable version "2019.6", minimum required is "2018") Here is a list of the errors ../libcsg/libvotca_csg.so.7: undefined reference to .collect2: error: ld returned 1 exit status |
I'll look into this to make sure I'm not doing something wonky with the files in my system library/includes. This passes the ci but I cann't build it locally. |
@junghans what versions of gromacs are being used in the ci? |
We build against:
|
There is a problem with the FindGromacs cmake module. Recently the gromacs has switched the api versioning system. Current versions of gromacs are now versioning starting at version 0 which breaks our current cmake module. |
Also using the spack gromacs causes problems because it is built with openmpi, gromacs_mpi and libgromacs_mpi need to be added as possible options. I'm working on a solution but welcome feedback. |
There is something wrong, in spack votca-csg depends on gromacs without mpi: https://github.com/spack/spack/blob/a20ba315f57bcbbb73838d1b67a15a9e14d580cd/var/spack/repos/builtin/packages/votca-csg/package.py#L35 |
Remember that we have two mechanisms to detect gromacs: |
Plus whatever you do make sure we can still use gromacs-2018/2019 as this is needed for the coarse-graining part. |
I have a question why can't we use the config method for also finding earlier versions? |
Because it is brocken in earlier versions. I just fixed that recently https://gitlab.com/gromacs/gromacs/-/merge_requests/48 |
Fixed in #554. |
@JensWehner you had trouble with gromacs file readers before, did you ever get the problem fixed. I'm getting tones of linker errors now as well.
The text was updated successfully, but these errors were encountered: