[petsc-dev] Why did you remove my CUDA version check!!!

[Matthew Knepley]

On Fri, Nov 5, 2010 at 1:57 PM, Matthew Knepley <knepley at gmail.com> wrote:

> On Fri, Nov 5, 2010 at 1:52 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>
>> because it was broken [as there was no
>> self.setCompilers.compilerVersionCUDA] - and I noticed a different
>> version check in setCompilers.py - and assumed thats the proper thing.
>>
>> But looks like vicotr made a mistake by adding in that check in
>> setCompilers.py.
>>
>> Still I don't see where self.setCompilers.compilerVersionCUDA was set
>> - and when that piece of cod removed..
>
>
> Dammit dammit dammit. Who is fucking with my code. It was in
> setCompilers.py.
> Everyone stop fucking with this while I fix it.
>

Okay, now in setCompilers.py, we set the CUDA version. As Barry pointed out
before,
this should be done for all compilers and packages:

            self.compilerVersionCUDA = compilerVersion[i].strip(',')

and that is checked in cuda.py. Works for me.

  Matt


>     Matt
>
>
>>
>> Satish
>>
>> On Fri, 5 Nov 2010, Matthew Knepley wrote:
>>
>> > That was the correct one. I took the one out
>> > of setCompilers.py for a reason.
>> >
>> >    Matt
>> >
>> >
>>
>>
>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
>



-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101105/f2c36ecc/attachment.html>