Re: Adding MPI back to Boost

2014-12-17 Thread Sean Farley
Anyone opposed to me pushes the proposed changes and marking them fixed? Sean Farley writes: Ryan Schmidt writes: On Dec 14, 2014, at 12:21 PM, Sean Farley wrote: Ryan Schmidt writes: So, this would add clang33, clang34, clang35 variants, for example? But these would be different from

Adding MPI back to Boost

2014-12-14 Thread Sean Farley
So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan tried to fix with r125939: https://trac.macports.org/changeset/125939 It seems instead that the fix is just to remove the gcc variants: mpi.setup -gcc

Re: Adding MPI back to Boost

2014-12-14 Thread Mark Moll
On Dec 14, 2014, at 2:28 AM, Sean Farley s...@macports.org wrote: So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan tried to fix with r125939: https://trac.macports.org/changeset/125939 It seems

Re: Adding MPI back to Boost

2014-12-14 Thread Ryan Schmidt
On Dec 14, 2014, at 2:28 AM, Sean Farley wrote: So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan tried to fix with r125939: https://trac.macports.org/changeset/125939 It seems instead that the

Re: Adding MPI back to Boost

2014-12-14 Thread Sean Farley
Mark Moll writes: On Dec 14, 2014, at 2:28 AM, Sean Farley s...@macports.org wrote: So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan tried to fix with r125939:

Re: Adding MPI back to Boost

2014-12-14 Thread Sean Farley
Ryan Schmidt writes: On Dec 14, 2014, at 2:28 AM, Sean Farley wrote: So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan tried to fix with r125939: https://trac.macports.org/changeset/125939 It

Re: Adding MPI back to Boost

2014-12-14 Thread Ryan Schmidt
On Dec 14, 2014, at 11:41 AM, Sean Farley wrote: Ryan Schmidt writes: On Dec 14, 2014, at 2:28 AM, Sean Farley wrote: So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan tried to fix with r125939:

Re: Adding MPI back to Boost

2014-12-14 Thread Sean Farley
Ryan Schmidt writes: On Dec 14, 2014, at 11:41 AM, Sean Farley wrote: Ryan Schmidt writes: On Dec 14, 2014, at 2:28 AM, Sean Farley wrote: So, I've added support into the compilers portgroup for working with the compiler.blacklist variable but that doesn't fix the issue that Ryan

Re: Adding MPI back to Boost

2014-12-14 Thread Ryan Schmidt
On Dec 14, 2014, at 12:21 PM, Sean Farley wrote: Ryan Schmidt writes: So, this would add clang33, clang34, clang35 variants, for example? But these would be different from the clang 3.x provided by Xcode in some way? The MacPorts clang ports would be able to use MPI somehow, while Xcode

Re: Adding MPI back to Boost

2014-12-14 Thread Eric A. Borisch
On Sunday, December 14, 2014, Ryan Schmidt ryandes...@macports.org wrote: On Dec 14, 2014, at 12:21 PM, Sean Farley wrote: Ryan Schmidt writes: So, this would add clang33, clang34, clang35 variants, for example? But these would be different from the clang 3.x provided by Xcode in some

Re: Adding MPI back to Boost

2014-12-14 Thread Sean Farley
Ryan Schmidt writes: On Dec 14, 2014, at 12:21 PM, Sean Farley wrote: Ryan Schmidt writes: So, this would add clang33, clang34, clang35 variants, for example? But these would be different from the clang 3.x provided by Xcode in some way? The MacPorts clang ports would be able to use