[petsc-users] Unable to configure PETSc with CUDA: Problem with thrust directory

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> On Fri, 29 Aug 2014, Dominic Meiser wrote:
>
>> On 08/29/2014 08:31 AM, Matthew Knepley wrote:
>> > On Fri, Aug 29, 2014 at 9:35 AM, Dominic Meiser <dmeiser at txcorp.com
>> > <mailto:dmeiser at txcorp.com>> wrote:
>
>> > >     Dominic, I think that thrust.py should depend on cuda.py. Do you
>> > >     know why it does not?
>> >     In principle you are right, thrust.py should depend on cuda.py.
>> >
>> >     However, in my opinion, thrust.py should go away as a separate
>> >     package altogether. Thrust is shipped as part of any recent
>> >     version of the cuda toolkit (I forget since which version, Paul
>> >     might know) and it's always installed in
>> >     $CUDA_TOOLKIT_ROOT/include/thrust. Thus we can automatically
>> >     deduct the thrust location from the cuda location. Thrust should
>> >     be considered part of cuda.
>
> I also think it should be removed.

Agreed.  If it was correct to consolidate umfpack, cholmod, etc., into
suitesparse, then there is no question that thrust should be
consolidated into cuda.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20140829/a0f44297/attachment.pgp>