[MacPorts] #40375: new mpich +gcc47 uses clang
MacPorts
noreply at macports.org
Wed Sep 11 20:17:10 PDT 2013
#40375: new mpich +gcc47 uses clang
----------------------------+------------------------
Reporter: beany_kelly@… | Owner: eborisch@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.0
Resolution: | Keywords:
Port: mpich |
----------------------------+------------------------
Changes (by eborisch@…):
* cc: dweber@…, hum@…, mmoll@…, ram@…, takeshi@… (added)
Comment:
I've got a set of changes ready over here
[diff:users/eborisch/dports at 110423:110971] that splits mpich and mpich-
devel up into a set of subparts. A user can either use mpich and family or
mpich-devel and family.
For each set, there is a mpich[-devel]-default that installs the headers
as well as a set if '-mp' suffixed binaries and lib/mpich[-devel]-mp/
libraries. Any port should depend upon and use bin/mpicc-mp and friends.
These will use the MacPorts' default c/c++ compilers, and a gccXX-based
fortran using 'fortran recipe' variants.
The other (mpich-clangXX, mpich-llvm, etc) subports wrap the specified
compiler (also with the fortran recipe for the non-gccXX flavors, and with
a default +fortran for those) and are intended for users that are
interested in using mpich for development of MPI tools outside the scope
of MacPorts and want a particular compiler for "reasons."
I've CC'd maintainers of ports that depend on mpich. As you'll see in the
changeset above I've got changes in place for those ports, but to be
honest, I haven't built every single one of them. Please take a look and
let me know if you have any concerns before I merge these changes into
trunk.
--
Ticket URL: <https://trac.macports.org/ticket/40375#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list