#40375: new mpich +gcc47 uses clang -----------------------------+-------------------------------- Reporter: beany_kelly@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: mpich clang gcc | Port: mpich -----------------------------+-------------------------------- Hi. I don't know if this really counts as a defect, but it's making life harder for me. Back in February (ticket #38065), I encountered problems with OpenMPI that were related to its use of clang for the C/C++ parts, instead of gcc/g++ (Fortran stayed GNU). At the end of this, I moved to MPICH precisely because I could avoid clang. Now I find that my recently upgraded "mpich +gcc47" (on Mountain Lion) is now clang-ified. Is there no way of avoiding it? I see that the *option* of bundling the clang version was discussed in ticket #39428, but in the last comment (8 weeks ago), it seemed merely to be a suggestion. -- Ticket URL: <https://trac.macports.org/ticket/40375> MacPorts <http://www.macports.org/> Ports system for OS X