[MacPorts] #38319: openmpi @1.6.4 +gcc45 non-standard names for executables

[MacPorts]

#38319: openmpi @1.6.4 +gcc45 non-standard names for executables
--------------------------+-------------------
  Reporter:  dstrubbe@…   |      Owner:  mww@…
      Type:  enhancement  |     Status:  new
  Priority:  Low          |  Milestone:
 Component:  ports        |    Version:  2.1.3
Resolution:               |   Keywords:
      Port:  openmpi      |
--------------------------+-------------------
Changes (by ryandesign@…):

 * owner:  macports-tickets@… => mww@…


Old description:

> The standard names for executables from OpenMPI are mpif90, mpif77,
> mpicc, mpirun, mpiexec. However, the ones provided by the openmpi port
> are all prefixed with "open", i.e. openmpif90 etc. I suggest this should
> be made clear somewhere in the port description, or alternately use the
> standard names (maybe the names were chosen to avoid conflict with
> mpich). I only discovered the actual names by reading through some
> tickets about this port. For example, the 'variants' output lists
> specifically the standard names, which are NOT the ones created by the
> port.
>
> openmpi has the variants:
>    g95: build mpif77 and mpif90 using g95
>      * conflicts with gcc43 gcc44 gcc45 gcc46 gcc47
>    gcc43: build mpif77 and mpif90 using gcc43
>      * conflicts with g95 gcc44 gcc45 gcc46 gcc47
>    gcc44: build mpif77 and mpif90 using gcc44
>      * conflicts with g95 gcc43 gcc45 gcc46 gcc47
> [+]gcc45: build mpif77 and mpif90 using gcc45
>      * conflicts with g95 gcc43 gcc44 gcc46 gcc47
>    gcc46: build mpif77 and mpif90 using gcc46
>      * conflicts with g95 gcc43 gcc44 gcc45 gcc47
>    gcc47: build mpif77 and mpif90 using gcc47
>      * conflicts with g95 gcc43 gcc44 gcc45 gcc46
>    threads: enable threads for MPI applications
>    valgrind: enable valgrind support
>
> I am using OSX 10.8.2 and Xcode 4.6.

New description:

 The standard names for executables from OpenMPI are mpif90, mpif77, mpicc,
 mpirun, mpiexec. However, the ones provided by the openmpi port are all
 prefixed with "open", i.e. openmpif90 etc. I suggest this should be made
 clear somewhere in the port description, or alternately use the standard
 names (maybe the names were chosen to avoid conflict with mpich). I only
 discovered the actual names by reading through some tickets about this
 port. For example, the 'variants' output lists specifically the standard
 names, which are NOT the ones created by the port.

 {{{
 openmpi has the variants:
    g95: build mpif77 and mpif90 using g95
      * conflicts with gcc43 gcc44 gcc45 gcc46 gcc47
    gcc43: build mpif77 and mpif90 using gcc43
      * conflicts with g95 gcc44 gcc45 gcc46 gcc47
    gcc44: build mpif77 and mpif90 using gcc44
      * conflicts with g95 gcc43 gcc45 gcc46 gcc47
 [+]gcc45: build mpif77 and mpif90 using gcc45
      * conflicts with g95 gcc43 gcc44 gcc46 gcc47
    gcc46: build mpif77 and mpif90 using gcc46
      * conflicts with g95 gcc43 gcc44 gcc45 gcc47
    gcc47: build mpif77 and mpif90 using gcc47
      * conflicts with g95 gcc43 gcc44 gcc45 gcc46
    threads: enable threads for MPI applications
    valgrind: enable valgrind support
 }}}

 I am using OSX 10.8.2 and Xcode 4.6.

--

Comment:

 Yes I would imagine the names are changed to avoid conflicts. But it's
 been that way ever since the port was first added in r14861 over seven
 years ago. It does seem like the variant descriptions (which were added in
 r35330) should show the correct filenames. Note that you can always
 discover what files a port installs by using e.g. "port contents openmpi".

-- 
Ticket URL: <https://trac.macports.org/ticket/38319#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X