[MacPorts] #51600: hdf4, hdf5, hdf5-18: h4cc, h5cc, h5c++, h5cc-18, h5c++-18 contain directives to use ccache
MacPorts
noreply at macports.org
Thu Jun 23 17:45:16 PDT 2016
- Previous message: [MacPorts] #51600: hdf4, hdf5, hdf5-18: h4cc, h5cc, h5c++, h5cc-18, h5c++-18 contain directives to use ccache
- Next message: [MacPorts] #51600: hdf4, hdf5, hdf5-18: h4cc, h5cc, h5c++, h5cc-18, h5c++-18 contain directives to use ccache
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
#51600: hdf4, hdf5, hdf5-18: h4cc, h5cc, h5c++, h5cc-18, h5c++-18 contain
directives to use ccache
----------------------------------+-----------------------
Reporter: ryandesign@… | Owner: takeshi@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.99
Resolution: | Keywords:
Port: hdf4, hdf5, hdf5-18 |
----------------------------------+-----------------------
Comment (by takeshi@…):
With ccache {{{CC}}} is set {{{ccache ${configiure.cc}}}}. I couldn't
figure out which environmental variable contains the path to C compiler
without {{{ccache}}}. So I simply remove the string {{{ccache }}} in
{{{h4cc}}} or in {{{h5cc}}}. Stopped using {{{h4cc}}} in {{{hdfeos}}}.
Left {{{hdfeos5}}} as it is because of MPI variants. Done in r149527.
--
Ticket URL: <https://trac.macports.org/ticket/51600#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X
- Previous message: [MacPorts] #51600: hdf4, hdf5, hdf5-18: h4cc, h5cc, h5c++, h5cc-18, h5c++-18 contain directives to use ccache
- Next message: [MacPorts] #51600: hdf4, hdf5, hdf5-18: h4cc, h5cc, h5c++, h5cc-18, h5c++-18 contain directives to use ccache
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the macports-tickets
mailing list