Opened 9 years ago

Last modified 8 years ago

#50782 closed defect

ncarg: fails to build out of the box and on build box — at Initial Version

Reported by: petrrr Owned by: tenomoto (Takeshi Enomoto)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: mamoll (Mark Moll)
Port: ncarg hdf5 hdfeos5 wgrib2 vis5d esmf

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?

Change History (0)

Note: See TracTickets for help on using tickets.