[MacPorts] #42220: py-netcdf4 @1.0.4_1: build failure when using ccache
MacPorts
noreply at macports.org
Mon Sep 21 13:52:08 PDT 2015
#42220: py-netcdf4 @1.0.4_1: build failure when using ccache
-------------------------+--------------------
Reporter: egall@… | Owner: sean@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: py-netcdf4 |
-------------------------+--------------------
Comment (by sean@…):
Replying to [comment:15 ryandesign@…]:
> I fixed the immediate problem in r140527, but I'm not comfortable with
the way this port works. It is not MacPorts custom for a port to build
itself differently depending on how another port was built, but that's
what py-netcdf4 does: it chooses which compiler to use based on the
compiler that was used for netcdf. With netcdf it's possible to discover
what compiler was used by checking which variants are selected in "port
installed netcdf", but py-netcdf4 doesn't have compiler variants so that's
not possible. That would also mean that if a user gets a binary from our
packages server it might have been built with a different compiler than
the netcdf on the user's system. If it's really so important that py-
netcdf4 uses the same compiler as netcdf, then py-netcdf4 needs to get the
same variants that netcdf has, and the require_active_variants procedure
in the active_variants 1.1 portgroup needs to be used to ensure the
variants the user has selected for the two ports match.
Almost certainly, this (and any other port that depends on hdf5) needs to
use the mpi portgroup so that the compilers line up. I truly hate compiler
wrappers. I can try to look at revamping the py-netcdf portfile but don't
know when I'll have time.
--
Ticket URL: <https://trac.macports.org/ticket/42220#comment:17>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list