Discussion:
port variants
(too old to reply)
Mark Brethen
2018-11-16 03:22:14 UTC
Permalink
Why don’t 'port info’ and ‘port variants’ list the same variants available for that port? For instance,

brethen-air:ports marbre$ port info getdp
getdp @3.0.3 (science, math)
Variants: [+]accelerate, atlas, clang33, clang34, clang37, clang38, clang39, clang40, clang50, clang60, clang70, debug, g95, [+]gfortran, [+]gmsh, mpich, mpich_devel, openblas, openmpi, openmpi_devel, petsc, [+]python27,
python36, python37, universal

Description: GetDP is a free finite element solver using mixed elements to discretize de Rham-type complexes in one, two and three dimensions.
Homepage: http://getdp.info

Build Dependencies: cmake, gcc8
Library Dependencies: arpack, gsl, hpddm, vecLibFort, libgcc, python27, gmsh
Platforms: darwin
License: GPL-2+
Maintainers: Email: ***@macports.org, GitHub: MarcusCalhoun-Lopez
Policy: openmaintainer
brethen-air:ports marbre$ port variants gmsh
gmsh has the variants:
[+]accelerate: Build with linear algebra from built-in Accelerate framework
* conflicts with atlas openblas
atlas: Build with linear algebra from ATLAS
* conflicts with accelerate openblas
clang33: Build using the MacPorts clang 3.3 compiler
* conflicts with clang34 clang37 clang38 clang39 clang40 clang50 clang60 clang70
clang34: Build using the MacPorts clang 3.4 compiler
* conflicts with clang33 clang37 clang38 clang39 clang40 clang50 clang60 clang70
clang37: Build using the MacPorts clang 3.7 compiler
* conflicts with clang33 clang34 clang38 clang39 clang40 clang50 clang60 clang70
clang38: Build using the MacPorts clang 3.8 compiler
* conflicts with clang33 clang34 clang37 clang39 clang40 clang50 clang60 clang70
clang39: Build using the MacPorts clang 3.9 compiler
* conflicts with clang33 clang34 clang37 clang38 clang40 clang50 clang60 clang70
clang40: Build using the MacPorts clang 4.0 compiler
* conflicts with clang33 clang34 clang37 clang38 clang39 clang50 clang60 clang70
clang50: Build using the MacPorts clang 5.0 compiler
* conflicts with clang33 clang34 clang37 clang38 clang39 clang40 clang60 clang70
clang60: Build using the MacPorts clang 6.0 compiler
* conflicts with clang33 clang34 clang37 clang38 clang39 clang40 clang50 clang70
clang70: Build using the MacPorts clang 7.0 compiler
* conflicts with clang33 clang34 clang37 clang38 clang39 clang40 clang50 clang60
debug: Enable debug binaries
docs: build documentation
g95: Build using the g95 Fortran compiler
* conflicts with gfortran
getdp: Enable GetDP solver
gfortran: Build using the MacPorts gcc 8 Fortran compiler
* conflicts with g95 g95
mpich: Build using the MPICH compiler
* conflicts with mpich_devel openmpi openmpi_devel
mpich_devel: Build using the MPICH-devel compiler
* conflicts with mpich openmpi openmpi_devel
openblas: Build with linear algebra from OpenBLAS
* conflicts with accelerate atlas
openmpi: Build using the OpenMPI compiler
* conflicts with mpich mpich_devel openmpi_devel
openmpi_devel: Build using the OpenMPI-devel compiler
* conflicts with mpich mpich_devel openmpi
universal: Build for multiple architectures

compare docs and python variants.

Mark Brethen
***@gmail.com
Bill Cole
2018-11-16 04:44:56 UTC
Permalink
Post by Mark Brethen
Why don’t 'port info’ and ‘port variants’ list the same
variants available for that port? For instance,
Well...
Post by Mark Brethen
brethen-air:ports marbre$ port info getdp
brethen-air:ports marbre$ port variants gmsh
So I would not expect them to have the same variants.
--
Bill Cole
***@scconsult.com or ***@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
Loading...