Package Details: opencoarrays 2.7.0-1

Git Clone URL: https://aur.archlinux.org/opencoarrays.git (read-only)
Package Base: opencoarrays
Description: A transport layer for coarray Fortran compilers.
Upstream URL: http://www.opencoarrays.org/
Keywords: caf coarray fortran parallel
Licenses: BSD
Submitter: jamesclark
Maintainer: physkets
Last Packager: physkets
Votes: 4
Popularity: 1.190307
First Submitted: 2015-10-13 14:12
Last Updated: 2019-05-11 15:54

Pinned Comments

physkets commented on 2019-03-19 05:35

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

Latest Comments

1 2 Next › Last »

physkets commented on 2019-05-12 17:25

@backerman , yes, I did notice that, and have filed a bug, upstream. The issue is that they should be looking inside the $DESTDIR, but are instead looking directly in /usr/... and since we're building a package first and then installing it, the files aren't already there.

Also, I should've checked and then updated the package instead of the other way round. I will make sure to do that from the next time.

backerman commented on 2019-05-12 17:02

The build is failing for me in the package() function.

-- Generating SHA256 checksumed receipt for all installed assets
CMake Error at ████████████/.cache/aurman/opencoarrays/src/OpenCoarrays-2.7.0/cmake/InstallFileManifest.cmake:21 (file):
  file SHA256 failed to read file "/usr/share/man/man1/caf.1": No such file
  or directory
Call Stack (most recent call first):
  cmake_install.cmake:95 (include)

caf.1 does exist in the right place in the pkg directory.

zbeekman commented on 2019-03-25 18:16

I've got reproducible builds working on macOS but it seems the archiver is injecting the build path for AUR still. I'm testing on a Linux VM and hope to have a patch release out soon that will be fully reproducible and relocatable.

physkets commented on 2019-03-19 05:35

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

physkets commented on 2018-07-04 06:36

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

Anonymous comment on 2018-02-24 20:57

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

jamesclark commented on 2016-09-15 10:32

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.

horne.kyle commented on 2016-09-15 04:57

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

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

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