I have recently had trouble with versioning of hdf5 and netcdf4 and gfortran.
In trying to fix things, I uninstalled and reinstalled several ports. Now I
have a mismatch
between gfortran (gcc48) and netcdf-fortran:
when compiling a fortran program that uses netcdf library:
use netcdf
1
I'm in the post-OSX-upgrade phase and wonder if MacPorts couldn't be updated by
doing the usual port selfupdate port upgrade outdated sequence - possibly
with -f and -p to have the process come through?
Also (and I know this is off-topic), exactly how impossible is it to keep XCode
3.2.6
On Tue, Feb 18, 2014 at 10:21 AM, René J.V. Bertin rjvber...@gmail.comwrote:
I'm in the post-OSX-upgrade phase and wonder if MacPorts couldn't be
updated by doing the usual port selfupdate port upgrade outdated
sequence - possibly with -f and -p to have the process come through?
Hi,
I'm in the post-OSX-upgrade phase and wonder if MacPorts couldn't be updated
by doing the usual port selfupdate port upgrade outdated sequence -
possibly with -f and -p to have the process come through?
First: -p is considered harmful when installing ports. That's because MacPorts
On Feb 18, 2014, at 16:35, Clemens Lang wrote:
later on when mixing this port with binaries built by our buildbot which
expect the newer dependency version. So, in summary, don't use -p unless
everything you do is download stuff (which is really the only reason why it's
there in the
On Feb 18, 2014, at 17:23, René J.V. Bertin rjvber...@gmail.com wrote:
On Feb 18, 2014, at 16:35, Clemens Lang wrote:
later on when mixing this port with binaries built by our buildbot which
expect the newer dependency version. So, in summary, don't use -p unless
everything you do is
