Arch Linux User Repository

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 :

$ caf <filename.f90>
$ cafrun -n <num_images> ./a.out

The package compiles specifically using MPICH executables as placed by its AUR package. If you've modified that, you will have to make appropriate changes in the PKGBUILD.

If you have any compilers other than GCC installed, take care to check your PATH environment variable to ensure that '/usr/bin' has higher priority, before building this package. (You'll also have to have done this while installing mpich)

To use OpenCoarrays, do:

$ caf <filename.f90>
$ cafrun -n <num_images> ./a.out

The package now compiles specifically using MPICH executables as placed by its AUR package.

If you have any compilers other than GCC installed, take care to check your PATH environment variable to ensure that '/usr/bin' has higher priority. (You'll also have to have done this while installing mpich)

If you choose to install the 'mpich' and 'opencoarrays' AUR packages as is, without modifying the PKGBUIDs, then, to compile and run a Fortran program that uses coarrays, do:

$ /opt/mpich/bin/mpifort -fcoarray=lib <filename.f90> -lcaf_mpi
$ /opt/mpich/bin/mpirun -n <num_images> ./a.out

Add "-DCMAKE_INSTALL_LIBDIR=lib" to avoid it trying to overwrite the lib64 symlink

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.

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.

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...

Just to say, I have been testing the MPI implementations some more and switched to MPICH. This should be permanent.

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

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 :)

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!