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 wou
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 b
On Sunday, December 14, 2014, Ryan Schmidt 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 way?
> The M
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, whi
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 is
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
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/125
Mark Moll 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/12
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
> 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
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
Is
11 matches
Mail list logo