[MacPorts] #47806: OpenCoarrays @1.0

MacPorts noreply at macports.org
Tue Jun 16 10:37:30 PDT 2015

#47806: OpenCoarrays @1.0
  Reporter:  fanfarillo.gcc@…  |      Owner:  macports-tickets@…
      Type:  submission        |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.3.3
Resolution:                    |   Keywords:
      Port:  opencoarrays      |

Comment (by fanfarillo.gcc@…):

 Replying to [comment:11 ryandesign@…]:
 > I am looking into this now. I did not see your other messages before
 because I was not Cc'd on the ticket, but I'll Cc myself now since nobody
 else appears to be working on it.
 > The INSTALL file says cmake is the preferred build system here. Any
 reason why you didn't use that in the Portfile?

 The CMake support has been added after I proposed the Portfile.

 > We still haven't addressed the fact that we're not UsingTheRightCompiler
 and -arch flags here. Currently it tries to build with "gcc" (which could
 be anything on a user's system; we want RepeatableBuilds) and "mpicc"
 (which will not exist on user systems unless they have used "port select",
 and MacPorts ports are not allowed to use the results of "port select" in
 their own builds (and, with trace mode, would be prohibited from doing

 I'll check this tomorrow. Just to be clear, opencoarrays does not need
 gcc5 to build. Gcc5 does not need opencoarrays to compile a coarray
 Fortran code which uses carries. Gcc5 needs opencoarrays to create the
 executable of a coarray Fortran code (actually it needs opencoarray only
 for the multi-image coarray code).

 > So opencoarrays appears to require mpich in order to build. You've
 written the dependency to be on mpich-devel-gcc5, which depends on gcc5.
 Therefore we would not be able to accommodate #47426 which requests that
 opencoarrays be added as a dependency of gcc5, because that would
 introduce a circular dependency, which is not possible in MacPorts.
 > Any reason why you used mpich-devel-gcc5 (the potentially unstable
 development version) and not mpich-gcc5 (the stable version)? If either
 would work, we should use a [ticket:14540 path:-style dependency] (instead
 of a port:-style one) to allow the user to choose between the development
 or stable version, with preference for the stable one.

 We would like to keep the installation process as easy as possible (asking
 for a choice sounds less easy to me). Let's just use mpich-gcc5.

 > The port claims to download version 1.0 of the software, but the
 opencoarrays web site does not mention such a version. It just refers
 users to the github page to download. The github page doesn't have any
 tags. If this is really version 1.0, why isn't there a 1.0 tag in the
 repository? If the URL listed in the portfile's master_sites is an
 official download URL, why isn't it mentioned anywhere on the opencoarrays
 web site?

 Good questions. The tarball currently available from macport was a
 candidate version now obsolete. The plan was to release OpenCoarrays 1.0
 as soon as this port was accepted. We still plan to do that; I should be
 able to work on the port tomorrow, after that, if all the changes will be
 accepted we can post the tarball of OpenCoarrays 1.0 on opencoarrays.org.

 > I tried adding a universal variant but it failed because the mpich
 dependency doesn't have a universal variant.

Ticket URL: <https://trac.macports.org/ticket/47806#comment:16>
MacPorts <https://www.macports.org/>
Ports system for OS X

More information about the macports-tickets mailing list