Opened 4 years ago
Closed 4 years ago
#60597 closed defect (fixed)
openmpi @4.0.1_1: openmpi-clangXX - the list of variants doesn't mention clang
| Reported by: | aivazis (Michael Aivazis) | Owned by: | aivazis (Michael Aivazis) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | mascguy (Christopher Nielsen) | |
| Port: | openmpi-clang |
Description
None of the openmpi clang supports have an accurate list of variants. clang is not mentioned
% port info openmpi-clang90
openmpi-clang90 @4.0.1_1 (science, parallel, net)
Variants: g95, [+]gcc10, gcc44, gcc45, gcc46, gcc47, gcc48, gcc49, gcc5, gcc6, gcc7,
gcc8, gcc9, universal, valgrind
Description: Open MPI is a project combining technologies and resources from several other
projects (FT-MPI, LA-MPI, LAM/MPI, and PACX-MPI) in order to build the best
MPI library available. A completely new MPI-2 compliant implementation, Open
MPI offers advantages for system and software vendors, application developers
and computer science researchers.
THIS SUBPORT WRAPS clang90's C/C++ (AND THE FORTRAN COMPILER SELECTED BY THE
VARIANT, IF ANY)
Homepage: https://www.open-mpi.org/
Build Dependencies: pkgconfig, gcc10, clang-9.0
Library Dependencies: hwloc, gcc10, libgcc, libgcc10
Runtime Dependencies: mpi_select, mpi-doc
Platforms: darwin
License: BSD
Maintainers: none
Change History (7)
comment:1 Changed 4 years ago by aivazis (Michael Aivazis)
| Owner: | set to aivazis |
|---|---|
| Status: | new → assigned |
comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
The description already says:
THIS SUBPORT WRAPS clang90's C/C++ (AND THE FORTRAN COMPILER SELECTED BY THE VARIANT, IF ANY)
Is that not clear?
comment:3 Changed 4 years ago by mascguy (Christopher Nielsen)
If there's any work involved, I'll take this. But there doesn't seem to be an issue here...?
comment:4 follow-up: 5 Changed 4 years ago by aivazis (Michael Aivazis)
I don't think there is actual work involved here, beyond perhaps a trivial adjustment to the port description so that it mentions what the intent of the port is. On a quick read of the description, all you see is a list of gcc choices and the openmpi project boilerplate. The important sentence that explains what the port is for is easy to miss, even though it is in all caps further down. I was a bit confused, and I'm guessing others might be also.
Feel free to close this if you feel the port description is fine as is.
comment:5 Changed 4 years ago by mascguy (Christopher Nielsen)
Replying to aivazis:
I don't think there is actual work involved here, beyond perhaps a trivial adjustment to the port description so that it mentions what the intent of the port is. On a quick read of the description, all you see is a list of gcc choices and the openmpi project boilerplate. The important sentence that explains what the port is for is easy to miss, even though it is in all caps further down. I was a bit confused, and I'm guessing others might be also.
Feel free to close this if you feel the port description is fine as is.
Whenever we can easily reduce confusion -- particularly by a simple description change -- I'm on-board.
Ryan/Anyone, do you folks have any objections to tweaking the description a bit? We'll propose the changes here first, to build consensus.
comment:6 Changed 4 years ago by mascguy (Christopher Nielsen)
| Cc: | mascguy added |
|---|
comment:7 Changed 4 years ago by Christopher Nielsen <mascguy@…>
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Variants are used to specify the package that provides
gfortran. Is there an easy way to document this so fewer people fall in this trap?