#50782: ncarg: fails to build out of the box and on build box ---------------------------------------------------+----------------------- Reporter: petr@… | Owner: takeshi@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: ncarg hdf5 hdfeos5 wgrib2 vis5d esmf | ---------------------------------------------------+----------------------- Description changed by petr@…: Old description:
Currently ncarg would not build out of the box and fails on the buildbots as well, due to conflicting variant requirements or lack of propagation of this requirement.
On a clean install, cleaned down to hdf5 (included), I get the following error message:
{{{ Error: Install hdf5 +gcc5 Error: org.macports.fetch for port ncarg returned: hdf5 +gcc5 not installed Warning: targets not executed for ncarg: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port ncarg for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_science_ncarg/ncarg/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ncarg failed }}}
The reason for this is that `ncarg`'s dependencies -- notably `hdfeos5` `wgrib2` `vis5d` and `esmf` -- tight in `hdf5`, which however is installed by default without `+gcc5` variant, while `ncarg` itself requires this variant.
{{{ hdf5 @1.8.16_2+cxx+hl }}}
{{{ The following ports are dependent on hdf5: hdfeos5 netcdf netcdf-fortran esmf vis5d wgrib2 }}}
Why this variant is required by `ncarg` in the first place? Would it be an option set the default of `hdf5` to this variant as well, to minimize the probability of conflicts? Otherwise, would it be an option to propagate the +gcc5 variant down the chain of dependencies?
New description: Currently ncarg would not build out of the box and fails on the buildbots as well, due to conflicting variant requirements or lack of propagation of this requirement. On a clean install, cleaned down to hdf5 (included), I get the following error message: {{{ Error: Install hdf5 +gcc5 Error: org.macports.fetch for port ncarg returned: hdf5 +gcc5 not installed Warning: targets not executed for ncarg: org.macports.activate org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port ncarg for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_science_ncarg/ncarg/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port ncarg failed }}} The reason for this is that `ncarg`'s dependencies -- notably `hdfeos5` `wgrib2` `vis5d` and `esmf` -- tight in `hdf5`, which however is installed by default without `+gcc5` variant, while `ncarg` itself requires this variant. This is what I get after the failure. `hdf5` was newly installed w/o the `+hdf5` variant: {{{ hdf5 @1.8.16_2+cxx+hl }}} Here the ports which cause to install it, so `hdf5` is not tight in directly by ncarg, but through its dependencies: {{{ % port rdependents hdf5 # after the failure The following ports are dependent on hdf5: hdfeos5 netcdf netcdf-fortran esmf vis5d wgrib2 }}} Why this variant is required by `ncarg` in the first place? Would it be an option set the default of `hdf5` to this variant as well, to minimize the probability of conflicts? Otherwise, would it be an option to propagate the +gcc5 variant down the chain of dependencies? -- -- Ticket URL: <https://trac.macports.org/ticket/50782#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X