The developers on OpenCoarrays recommend MPICH, so I will keep using that.
I updated the package to 1.7.2, I didn't seem to get a notification about the release.
Search Criteria
Package Details: opencoarrays 2.10.2-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/opencoarrays.git (read-only, click to copy) |
---|---|
Package Base: | opencoarrays |
Description: | A transport layer for coarray Fortran compilers. |
Upstream URL: | https://github.com/sourceryinstitute/OpenCoarrays |
Keywords: | caf coarray fortran parallel |
Licenses: | BSD |
Conflicts: | opencoarrays-git, opencoarrays-mpich-git |
Submitter: | jamesclark |
Maintainer: | banana-bred |
Last Packager: | banana-bred |
Votes: | 10 |
Popularity: | 0.041492 |
First Submitted: | 2015-10-13 14:12 (UTC) |
Last Updated: | 2024-10-09 23:31 (UTC) |
Dependencies (3)
- openmpi (openmpi-gitAUR)
- cmake (cmake-gitAUR) (make)
- gcc-fortran (gcc-fortran-gitAUR, gcc11-fortranAUR, gcc-fortran-snapshotAUR) (make)
Required by (0)
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3
jamesclark commented on 2016-09-15 10:32 (UTC)
horne.kyle commented on 2016-09-15 04:57 (UTC)
I have an updated PKGBUILD which usees 1.7.2, but I also changed MPI to use openmpi since that is in the main repositories. I can send it to you if you like.
zbeekman commented on 2016-07-25 19:38 (UTC)
The latest version of OpenCoarrays (1.6.2) has been released. I would love it if someone could please update the package definition, or at least give me a quick tutorial on how to do it myself. The one caveat is that I am not running Arch Linux, so if I update it, there will be no testing...
jamesclark commented on 2015-12-16 20:56 (UTC) (edited on 2015-12-16 21:26 (UTC) by jamesclark)
Just to say, I have been testing the MPI implementations some more and switched to MPICH. This should be permanent.
szaghi commented on 2015-10-21 03:40 (UTC)
Hi James,
Thank you very much for quick replay. I see that OpenMPI is only a dependency and it is not used for building the package, indeed I have now installed your package and successfully used with MPICH compiled manually.
On the behalf of the OpenCoarrays team thank very much for your work.
Stefano
jamesclark commented on 2015-10-20 16:41 (UTC)
Hello,
I am not sure about exact download statistics, but in the information above there is a "votes" and "popularity" section.
I used OpenMPI purely because that is what I have been using. I wanted to say you need OpenMPI or MPICH, but the this functionality isn't built in to PKGBUILDs. I would be willing to change this dependency if there are some good reasons.
Let me know how you get on with the package :)
szaghi commented on 2015-10-20 07:52 (UTC) (edited on 2015-10-20 07:54 (UTC) by szaghi)
Dear James,
the development team of OpenCoarrays (with which I have talked to) are very grateful to you for maintaining this AUR package build (me too!).
They have a question for you (they do not use Arch Linux thus ask me to work as *ambassador*): is it possible to obtain statistics on this AUR package downloads? OpenCoarrays is developed with love by a no-profit Institute (sourceryinstitute) for which this kind of statics is relevant for obtaining future funding.
Besides, I have a personal question. Reading your PKBUILD I see that you select OpenMPI rather MPICH. OpenCoarrays official instructions suggest MPICH as the preferred MPI back-end: why do you select OpenMPI?
Thank you very much for your great work, it is very appreciated!
Pinned Comments
banana-bred commented on 2024-02-08 18:19 (UTC)
This package now uses Open MPI instead of MPICH to avoid build issues. Should the MPICH build issues be resolved, I might make a separate opencoarrays-mpich package which uses MPICH.
To use OpenCoarrays :