Search Criteria
Package Details: gromacs 2021.2-3
| Git Clone URL: | https://aur.archlinux.org/gromacs.git (read-only, click to copy) |
|---|---|
| Package Base: | gromacs |
| Description: | A versatile package to perform molecular dynamics, i.e. simulate the Newtonian equations of motion for systems with hundreds to millions of particles. |
| Upstream URL: | http://www.gromacs.org/ |
| Licenses: | |
| Submitter: | xyproto |
| Maintainer: | hseara |
| Last Packager: | hseara |
| Votes: | 20 |
| Popularity: | 0.000016 |
| First Submitted: | 2011-12-14 17:03 |
| Last Updated: | 2021-05-20 14:12 |
Dependencies (12)
- gcc10
- hwloc (hwloc1)
- lapack (openblas-lapack-git, lapack-tmg, flexiblas, openblas-lapack-static, atlas-lapack, lapack-git, armpl, openblas-lapack)
- zlib (zlib-static, zlib-git, zlib-asm, minizip-asm, zlib-ng-git, zlib-ng)
- cmake (cmake-git) (make)
- hwloc (hwloc1) (make)
- libxml2 (libxml2-linenum, libxml2-git) (make)
- cuda (cuda-11.0, cuda11.1) (optional) – Nvidia GPU support
- opencl-mesa (opencl-mesa-noglvnd, mesa-minimal-git, mesa-minimal+-git, mesa-git, mesa-d3d12) (optional) – OpenCL support for AMD GPU
- opencl-nvidia (opencl-nvidia-410xx, opencl-nvidia-340xx, opencl-nvidia-440xx, opencl-nvidia-full-vulkan-all, opencl-nvidia-390xx, opencl-nvidia-vulkan, opencl-nvidia-beta, opencl-nvidia-performance) (optional) – OpenCL support for Nvidia GPU
- perl (perl-git) (optional) – needed for demux.pl and xplor2gmx.pl
- vmd (vmd-bin) (optional) – Accesibility to other trajectory formats (ONLY WHEN COMPILING)
Latest Comments
1 2 3 4 5 6 ... Next › Last »
E3LDDfrK commented on 2020-03-24 08:27
@gardotd426 What changes did you make? Did you check this https://bbs.archlinux.org/viewtopic.php?pid=1870450#p1870450 ? I think adding options=(!buildflags) to PKGBUILD is the easiest way to solve this.
I think some people ignore that sometime people install the gromacs package to analyze the data without actually running the simulation on their computers. (In the sense that I use my old laptop that doesn't support AVX2 to analyze/manipulate the trajectories. Pretty sure I'm not alone in this.)
gardotd426 commented on 2020-03-23 08:13
This fails to build, even after changing /etc/makepkg.conf as suggested below. /proc/cpuinfo shows that my cpu does support avx2...
cat /proc/cpuinfo:
hseara commented on 2019-12-13 11:47
@brisvag Please recompile gromacs. hwloc has been updated from v1 to v2 which brakes gromacs installation. Recompiling gromacs solves the issue.
brisvag commented on 2019-12-10 14:09
When I try to use
gmx dumpon a.tpr, I get the following error:Indeed, the library is missing. Simply adding a symlink to
libhwloc.soadding.5at the end solves the issue. Shouldn't this be handled by the installation?E3LDDfrK commented on 2019-10-24 17:05
EDIT 3: A solution here: https://bbs.archlinux.org/viewtopic.php?pid=1870411#p1870411
I have the same error as @mefistofeles.
EDIT 2: And @malinke too. It's partly because my CPU doesn't support AVX2, I think. There's a double "-march=core-avx2 -march=native" when compiling fftw. It fails because my "-march=native" doesn't actually support AVX2.
I've also changed my /etc/makepkg.conf as @hseara suggested.
It's a Thinkpad X220 with Sandy Bridge, so I used -DGMX_SIMD=AVX_256 on my PKGBUILD. At least in my case, computer doesn't support avx2, so it failed to compile fftw. Not sure what to do here, it seems fftw is automatically compiled with "--enable-avx2". I'll try again later without DGMX_BUILD_OWN_FFTW=ON on the PKGBUILD.
EDIT 1: So it builds successfully when I replaced DGMX_BUILD_OWN_FFTW=ON with -DGMX_FFT_LIBRARY=fftw3 on the PKGBUILD. Not sure if using pacman-installed fftw with GROMACS will lead to problems later on.
For what it's worth, like @mefistofeles, I also tried to manually build the package using cmake and DGMX_BUILD_OWN_FFTW=ON, and it worked. I wonder what the problem is. From what I can tell, gromacs-2019.4/src/external/build-fftw/CMakeLists.txt says it will build fftw with only either just "--enable-sse2" or the whole "--enable-sse2;--enable-avx;--enable-avx2". The "--enable-avx" always comes with "--enable-avx2". But it worked this time, despite my CPU not supporting AVX 2. When running cmake, it also outputted:
Just for comparison. This line from manual install succeeds:
This line from aur using pikaur fails:
So possibly the double "-march" thing makes it fail? Just "-march=core-avx2" vs "-march=core-avx2 -march=native". Because my Sandy Bridge ("-march=native" part) doesn't actually support AVX2.
hseara commented on 2019-06-13 14:46
@mefistofeles, either your cpu does not support AVX2 (check in /proc/cpuinfo) or your /etc/makepkg.conf is not set to native architecture:
PS: -fstack-protector-strong in makepkg.conf is not needed
mefistofeles commented on 2019-05-21 20:42
For some reason using the following PKGBUILD fails compiling, check https://paste.rs/IqF
The error is in https://paste.rs/6W0
Specifically the part that says error: #error "compiling simd-avx2.h without avx2 support" when compiling FFTW.
The funny thing is that when I manually compile using "cmake .. -DGMX_GPU=ON -DGMX_SIMD=AVX2_256 -DGMX_BUILD_OWN_FFTW=ON" it works fine. Don't really know what is causing the error. Help appreciated.
BTW, using the -fstack-protector-strong in makepkg.conf didn't work. as suggested by @hseara
hseara commented on 2019-04-15 20:13
No longer needed in gromacs 2019.4
Installation notes
With cmake update to v3.14.x, gromacs is no longer capable of identifying correctly the CPU and therefore the appropriated SIMD level for compilation. If you want to compile gromacs with SIMD while the problem is not solved add the following option to PKGBUILD:
The KEYWORD depends on the SIMD support provided by your CPU.
Usage notes
roina commented on 2017-12-17 12:35
hseara, the current (2016.4 released September 15, 2017) doesn't works with CUDA in old systems. But new gromacs (2018-beta2 released December 12 2017) works perfectly with current PKGBUILD (gromacs 2016.4-2) and CUDA 9.1. So don't wait and update the version.
hseara commented on 2017-12-04 15:30
The current PKGBUILD works perfectly in new systems.
@manlinke: I have the feeling that at least part of your problem is Cuda related. You seem to have an "NVIDIA GeForce GTX 550 Ti" which is no longer supported by Cuda 9. That means that your code will compile well, but tests will fail. The only possible workaround which I'm using on an old system myself is to use Cuda 8 in your system instead of Cuda 9. It is not possible for me to deal with this issue as it is graphics card dependent. You can always disable CUDA "-DGMX_GPU=OFF".
@manlike: The following lines overriding the /etc/makepkg.conf defaults should take care of the avx2 issues:
export CFLAGS="-march=native -O2 -pipe -fstack-protector-strong"
export CXXFLAGS="${CFLAGS}"
Once you fix the Cuda issues, please check again if you have really avx2 issues.