Thank you Eric. Your suggestion with a "-f" got me back in the game.
I like the idea of consistent compilers throughout the tool chain build. I wish this was the default, ie. port install-gcc46 <packages>....and all packages from there on out are built with the version of gcc46. I guess use of llvm is for speedup, but the dedicated compiler would help with consistency. Thanks again, <>Srinath ================================= Srinath Vadlamani ================================= On Fri, Sep 7, 2012 at 8:17 AM, Eric A. Borisch <[email protected]>wrote: > On Thu, Sep 6, 2012 at 11:10 PM, Lawrence Velázquez > <[email protected]> wrote: > > On Sep 6, 2012, at 11:26 p.m., Srinath Vadlamani wrote: > > > >> This was not the case a few months ago, but now it is. > >> > >> Why? > > > > The openmpi variant now forces the use of the compiler that was used to > build openmpi. It conflicts with all gccXY variants. > > > > vq > > If you want hdf5-18 installed with gcc46's fortran and openmpi, do this: > > sudo port install openmpi +gcc46 (openmpif90 wraps gcc46's fortran) > sudo port install hdf5-18 +openmpi+fortran (uses openmpi(cc|cxx|f90) > as the compilers) > > Similarly for mpich2, but for mpich2, all the gccNN compilers > (c/c++/fort) are used, not just fortran. > > This was done to avoid failures when competing gccNN (or lack thereof) > versions were selected for mpich2/openmpi and hdf5-18 +openmpi / > +mpich2. > > -Eric >
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
