I’ve built them on linux (I have a student working on expanding this), and as far as I can
remember, I had to install CUDA, and that was all. I think I recall having to fix a problem
with build options for cmake, and I will check to see if I committed this fix this afternoon.

best regards
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 3 Dec 2015, at 09:56, Anders Genell  wrote:
> 
> Dear list (especially Victor)!
> 
> Are there any build instructions for building csound with cuda opcodes on Linux avalable?
> I saw in some old thread at Nabble that Matti Koskinen seemed to have succeeded but couldn't interpret how he did so.
> 
> Regards,

I forgot: you should also set  BUILD_CUDA_OPCODES=1
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 3 Dec 2015, at 13:05, Anders Genell  wrote:
> 
> Well, the output from cmake doesn't say anything about cuda, so I suppose it's not included by default.
> 
> Regards,
> Anders
> 
> On Thu, Dec 3, 2015 at 2:02 PM, Anders Genell  wrote:
> Brilliant, thanks!
> I have CUDA installed since my attempt to build Octave with CUDA support, so that should be allright.
> I'll give it a go and see if it builds without extra cmake options.
> 
> Regards,
> Anders
> 
> On Thu, Dec 3, 2015 at 1:31 PM, Victor Lazzarini  wrote:
> I’ve built them on linux (I have a student working on expanding this), and as far as I can
> remember, I had to install CUDA, and that was all. I think I recall having to fix a problem
> with build options for cmake, and I will check to see if I committed this fix this afternoon.
> 
> best regards
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 3 Dec 2015, at 09:56, Anders Genell  wrote:
> >
> > Dear list (especially Victor)!
> >
> > Are there any build instructions for building csound with cuda opcodes on Linux avalable?
> > I saw in some old thread at Nabble that Matti Koskinen seemed to have succeeded but couldn't interpret how he did so.
> >
> > Regards,
> > Anders
> 

On 12/03/2015 08:05 AM, Anders Genell wrote:
> Well, the output from cmake doesn't say anything about cuda, so I 
> suppose it's not included by default.
>
>

Run

   ccmake .

in the build directory and set the CUDA build option to 1, then 
regenerate the makefile.

Best,

Oh, and I changed to csound option to refer to an .so instead of dylib.

I do however get some warnings:

WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop2.so: undefined symbol: cufftSetCompatibilityMode)

WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop5.so: undefined symbol: cufftSetCompatibilityMode)

Regards,

Anders

On Thu, Dec 3, 2015 at 2:46 PM, Anders Genell <anders.genell@gmail.com> wrote:

Actually I figured out that it was possible (and fairly easy) to add an option to cmake to enable the cuda build, and I replied so to this thread, but the list server thought I tried to change my list settings using the wrong address, so it bounced :-)

Now everything is dandy csound-wise.

Thank you, though!

Next thing is to try to combine parts stolen mostly from Victor to get cuda convolution running as a csladspa plug...

Regards,

Anders

On Thu, Dec 3, 2015 at 2:28 PM, Dave Phillips <dlphillips@woh.rr.com> wrote:

On 12/03/2015 08:05 AM, Anders Genell wrote:

Well, the output from cmake doesn't say anything about cuda, so I suppose it's not included by default.

Run

  ccmake .

in the build directory and set the CUDA build option to 1, then regenerate the makefile.

Best,

dp

yes this is what I meant. I need to commit my changes to make the build work correctly. Currently it is not linking to cufft, that is the problem.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 3 Dec 2015, at 14:39, Anders Genell <anders.genell@GMAIL.COM> wrote:

Oh, and I changed to csound option to refer to an .so instead of dylib.

I do however get some warnings:

WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop2.so: undefined symbol: cufftSetCompatibilityMode)

WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop5.so: undefined symbol: cufftSetCompatibilityMode)

Regards,

Anders

On Thu, Dec 3, 2015 at 2:46 PM, Anders Genell <anders.genell@gmail.com> wrote:

Actually I figured out that it was possible (and fairly easy) to add an option to cmake to enable the cuda build, and I replied so to this thread, but the list server thought I tried to change my list settings using the wrong address, so it bounced :-)

Now everything is dandy csound-wise.

Thank you, though!

Next thing is to try to combine parts stolen mostly from Victor to get cuda convolution running as a csladspa plug...

Regards,

Anders

On Thu, Dec 3, 2015 at 2:28 PM, Dave Phillips <dlphillips@woh.rr.com> wrote:

On 12/03/2015 08:05 AM, Anders Genell wrote:

Well, the output from cmake doesn't say anything about cuda, so I suppose it's not included by default.

Run

  ccmake .

in the build directory and set the CUDA build option to 1, then regenerate the makefile.

Best,

dp

Try it now.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 3 Dec 2015, at 14:50, Anders Genell  wrote:
> 
> Ah, ok, I see. 
> Well, it seems I'm good to go otherwise so I'll just patiently bide my time (arewethereyet?arewethereyet?arewethereyet?arewethereyet?arewethereyet?arewethereyet?arewethereyet?...)
> 
> Regards,
> Anders
> 
> 
> 3 dec. 2015 kl. 15:46 skrev Victor Lazzarini :
> 
>> yes this is what I meant. I need to commit my changes to make the build work correctly. Currently it is not linking to cufft, that is the problem.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>> On 3 Dec 2015, at 14:39, Anders Genell  wrote:
>> 
>>> Oh, and I changed to csound option to refer to an .so instead of dylib.
>>> I do however get some warnings:
>>> WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop2.so: undefined symbol: cufftSetCompatibilityMode)
>>> WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop5.so: undefined symbol: cufftSetCompatibilityMode)
>>> 
>>> Regards,
>>> Anders
>>> 
>>> On Thu, Dec 3, 2015 at 2:46 PM, Anders Genell  wrote:
>>> Actually I figured out that it was possible (and fairly easy) to add an option to cmake to enable the cuda build, and I replied so to this thread, but the list server thought I tried to change my list settings using the wrong address, so it bounced :-)
>>> Now everything is dandy csound-wise.
>>> 
>>> Thank you, though!
>>> 
>>> Next thing is to try to combine parts stolen mostly from Victor to get cuda convolution running as a csladspa plug...
>>> 
>>> Regards,
>>> Anders
>>> 
>>> On Thu, Dec 3, 2015 at 2:28 PM, Dave Phillips  wrote:
>>> On 12/03/2015 08:05 AM, Anders Genell wrote:
>>> Well, the output from cmake doesn't say anything about cuda, so I suppose it's not included by default.
>>> 
>>> 
>>> 
>>> Run
>>> 
>>>   ccmake .
>>> 
>>> in the build directory and set the CUDA build option to 1, then regenerate the makefile.
>>> 
>>> Best,
>>> 
>>> dp
>>> 

i guess you need to install nvidia-cuda-dev as well?
What is the minimal way to get the Cuda opcodes up and running?



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html

You need to use a table. How you load samples into it is your business. The simplest way is
using GEN01.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 3 Dec 2015, at 15:25, Anders Genell  wrote:
> 
> Works like a charm without warnings, thanks!
> 
> Btw, is it necessary to load the IR into an ftable, or can I use diskin for that too?
> Or could there be a version like pconvolve that can take a filename as argument directly?
> 
> Regards,
> Anders
> 
> On Thu, Dec 3, 2015 at 4:17 PM, Victor Lazzarini  wrote:
> Try it now.
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
> 
> > On 3 Dec 2015, at 14:50, Anders Genell  wrote:
> >
> > Ah, ok, I see.
> > Well, it seems I'm good to go otherwise so I'll just patiently bide my time (arewethereyet?arewethereyet?arewethereyet?arewethereyet?arewethereyet?arewethereyet?arewethereyet?...)
> >
> > Regards,
> > Anders
> >
> >
> > 3 dec. 2015 kl. 15:46 skrev Victor Lazzarini :
> >
> >> yes this is what I meant. I need to commit my changes to make the build work correctly. Currently it is not linking to cufft, that is the problem.
> >>
> >> Victor Lazzarini
> >> Dean of Arts, Celtic Studies, and Philosophy
> >> Maynooth University
> >> Ireland
> >>
> >> On 3 Dec 2015, at 14:39, Anders Genell  wrote:
> >>
> >>> Oh, and I changed to csound option to refer to an .so instead of dylib.
> >>> I do however get some warnings:
> >>> WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop2.so: undefined symbol: cufftSetCompatibilityMode)
> >>> WARNING: could not open library '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (/usr/local/lib/csound/plugins64-6.0/libcudaop5.so: undefined symbol: cufftSetCompatibilityMode)
> >>>
> >>> Regards,
> >>> Anders
> >>>
> >>> On Thu, Dec 3, 2015 at 2:46 PM, Anders Genell  wrote:
> >>> Actually I figured out that it was possible (and fairly easy) to add an option to cmake to enable the cuda build, and I replied so to this thread, but the list server thought I tried to change my list settings using the wrong address, so it bounced :-)
> >>> Now everything is dandy csound-wise.
> >>>
> >>> Thank you, though!
> >>>
> >>> Next thing is to try to combine parts stolen mostly from Victor to get cuda convolution running as a csladspa plug...
> >>>
> >>> Regards,
> >>> Anders
> >>>
> >>> On Thu, Dec 3, 2015 at 2:28 PM, Dave Phillips  wrote:
> >>> On 12/03/2015 08:05 AM, Anders Genell wrote:
> >>> Well, the output from cmake doesn't say anything about cuda, so I suppose it's not included by default.
> >>>
> >>>
> >>>
> >>> Run
> >>>
> >>>   ccmake .
> >>>
> >>> in the build directory and set the CUDA build option to 1, then regenerate the makefile.
> >>>
> >>> Best,
> >>>
> >>> dp
> >>>
> >>>

CUDA, from whatever package your system offers, and a nvidia GPU.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 3 Dec 2015, at 15:28, Menno Knevel  wrote:
> 
> i guess you need to install nvidia-cuda-dev as well?
> What is the minimal way to get the Cuda opcodes up and running?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html

Maybe the next step would be implementing support for raspberry pi gpu accelerated fft?

$5 and hardware acceleration is kind of crazy...

https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/

Regards

/Anders

On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

CUDA, from whatever package your system offers, and a nvidia GPU.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 3 Dec 2015, at 15:28, Menno Knevel <magknevel@GMAIL.COM> wrote:
>
> i guess you need to install nvidia-cuda-dev as well?
> What is the minimal way to get the Cuda opcodes up and running?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.

If it's nvidia-based, it will work. Otherwise, we will need to develop an opencl alternative.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 3 Dec 2015, at 16:14, Anders Genell <anders.genell@GMAIL.COM> wrote:

Maybe the next step would be implementing support for raspberry pi gpu accelerated fft?

$5 and hardware acceleration is kind of crazy...

https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/

Regards

/Anders

On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

CUDA, from whatever package your system offers, and a nvidia GPU.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 3 Dec 2015, at 15:28, Menno Knevel <magknevel@GMAIL.COM> wrote:
>
> i guess you need to install nvidia-cuda-dev as well?
> What is the minimal way to get the Cuda opcodes up and running?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.

I filed an issue regarding 3rd party FFT libraries:

https://github.com/csound/csound/issues/495

If we did do this, we could possibly use this person's RPi library
when building for RPi.

On Thu, Dec 3, 2015 at 12:25 PM, Anders Genell  wrote:
> If I understand correctly, which I almost certainly don't, it is neither...
>
> http://petewarden.com/2014/08/07/how-to-optimize-raspberry-pi-code-using-its-gpu/
>
> Regards,
> Anders
>
>
> 3 dec. 2015 kl. 18:07 skrev Victor Lazzarini :
>
> If it's nvidia-based, it will work. Otherwise, we will need to develop an
> opencl alternative.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 3 Dec 2015, at 16:14, Anders Genell  wrote:
>
> Maybe the next step would be implementing support for raspberry pi gpu
> accelerated fft?
> $5 and hardware acceleration is kind of crazy...
> https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/
> Regards
> /Anders
>
>
> On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini 
> wrote:
>>
>> CUDA, from whatever package your system offers, and a nvidia GPU.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 3 Dec 2015, at 15:28, Menno Knevel  wrote:
>> >
>> > i guess you need to install nvidia-cuda-dev as well?
>> > What is the minimal way to get the Cuda opcodes up and running?
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
>> > Sent from the Csound - Dev mailing list archive at Nabble.com.
>

If I understand correctly, which I almost certainly don't, it is neither...

http://petewarden.com/2014/08/07/how-to-optimize-raspberry-pi-code-using-its-gpu/

Regards,

Anders

3 dec. 2015 kl. 18:07 skrev Victor Lazzarini <Victor.Lazzarini@NUIM.IE>:

If it's nvidia-based, it will work. Otherwise, we will need to develop an opencl alternative.

Victor Lazzarini

Dean of Arts, Celtic Studies, and Philosophy

Maynooth University

Ireland

On 3 Dec 2015, at 16:14, Anders Genell <anders.genell@GMAIL.COM> wrote:

Maybe the next step would be implementing support for raspberry pi gpu accelerated fft?

$5 and hardware acceleration is kind of crazy...

https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/

Regards

/Anders

On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

CUDA, from whatever package your system offers, and a nvidia GPU.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 3 Dec 2015, at 15:28, Menno Knevel <magknevel@GMAIL.COM> wrote:
>
> i guess you need to install nvidia-cuda-dev as well?
> What is the minimal way to get the Cuda opcodes up and running?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.

That would be just perfect!
Regards,
Anders



> 3 dec. 2015 kl. 18:47 skrev Steven Yi :
> 
> I filed an issue regarding 3rd party FFT libraries:
> 
> https://github.com/csound/csound/issues/495
> 
> If we did do this, we could possibly use this person's RPi library
> when building for RPi.
> 
>> On Thu, Dec 3, 2015 at 12:25 PM, Anders Genell  wrote:
>> If I understand correctly, which I almost certainly don't, it is neither...
>> 
>> http://petewarden.com/2014/08/07/how-to-optimize-raspberry-pi-code-using-its-gpu/
>> 
>> Regards,
>> Anders
>> 
>> 
>> 3 dec. 2015 kl. 18:07 skrev Victor Lazzarini :
>> 
>> If it's nvidia-based, it will work. Otherwise, we will need to develop an
>> opencl alternative.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>> On 3 Dec 2015, at 16:14, Anders Genell  wrote:
>> 
>> Maybe the next step would be implementing support for raspberry pi gpu
>> accelerated fft?
>> $5 and hardware acceleration is kind of crazy...
>> https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/
>> Regards
>> /Anders
>> 
>> 
>> On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini 
>> wrote:
>>> 
>>> CUDA, from whatever package your system offers, and a nvidia GPU.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 3 Dec 2015, at 15:28, Menno Knevel  wrote:
>>>> 
>>>> i guess you need to install nvidia-cuda-dev as well?
>>>> What is the minimal way to get the Cuda opcodes up and running?
>>>> 
>>>> 
>>>> 
>>>> --
>>>> View this message in context:
>>>> http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
>>>> Sent from the Csound - Dev mailing list archive at Nabble.com.
>> 

Oh, I misread that blog entry.  It's not a library for FFT and it
doesn't look like the code is there to use as a library.  Not sure
that'd be simple for us to include as a 3rd party lib then for that
FFT issue I filed.

On Thu, Dec 3, 2015 at 6:41 PM, Victor Lazzarini
 wrote:
> This looks horrible, having to write hardware-dependent code in a custom
> assembler. No, I don't think so. By the time we get it right, the hardware
> has moved on.
>
> No, thanks.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 3 Dec 2015, at 17:25, Anders Genell  wrote:
>
> If I understand correctly, which I almost certainly don't, it is neither...
>
> http://petewarden.com/2014/08/07/how-to-optimize-raspberry-pi-code-using-its-gpu/
>
> Regards,
> Anders
>
>
> 3 dec. 2015 kl. 18:07 skrev Victor Lazzarini :
>
> If it's nvidia-based, it will work. Otherwise, we will need to develop an
> opencl alternative.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 3 Dec 2015, at 16:14, Anders Genell  wrote:
>
> Maybe the next step would be implementing support for raspberry pi gpu
> accelerated fft?
> $5 and hardware acceleration is kind of crazy...
> https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/
> Regards
> /Anders
>
>
> On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini 
> wrote:
>>
>> CUDA, from whatever package your system offers, and a nvidia GPU.
>> ========================
>> Dr Victor Lazzarini
>> Dean of Arts, Celtic Studies and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>> > On 3 Dec 2015, at 15:28, Menno Knevel  wrote:
>> >
>> > i guess you need to install nvidia-cuda-dev as well?
>> > What is the minimal way to get the Cuda opcodes up and running?
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
>> > Sent from the Csound - Dev mailing list archive at Nabble.com.
>

Actually, if we're talking small machines, the nvidia jetson gives you more bang for your buck. 0.5 dollars per gflop computation as
opposed to 1 dollar per gflop for the rpi1
according to this
https://rpiplayground.wordpress.com

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 3 Dec 2015, at 19:45, Steven Yi  wrote:
> 
> Oh, I misread that blog entry.  It's not a library for FFT and it
> doesn't look like the code is there to use as a library.  Not sure
> that'd be simple for us to include as a 3rd party lib then for that
> FFT issue I filed.
> 
> On Thu, Dec 3, 2015 at 6:41 PM, Victor Lazzarini
>  wrote:
>> This looks horrible, having to write hardware-dependent code in a custom
>> assembler. No, I don't think so. By the time we get it right, the hardware
>> has moved on.
>> 
>> No, thanks.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>> On 3 Dec 2015, at 17:25, Anders Genell  wrote:
>> 
>> If I understand correctly, which I almost certainly don't, it is neither...
>> 
>> http://petewarden.com/2014/08/07/how-to-optimize-raspberry-pi-code-using-its-gpu/
>> 
>> Regards,
>> Anders
>> 
>> 
>> 3 dec. 2015 kl. 18:07 skrev Victor Lazzarini :
>> 
>> If it's nvidia-based, it will work. Otherwise, we will need to develop an
>> opencl alternative.
>> 
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>> 
>> On 3 Dec 2015, at 16:14, Anders Genell  wrote:
>> 
>> Maybe the next step would be implementing support for raspberry pi gpu
>> accelerated fft?
>> $5 and hardware acceleration is kind of crazy...
>> https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/
>> Regards
>> /Anders
>> 
>> 
>> On Thu, Dec 3, 2015 at 4:42 PM, Victor Lazzarini 
>> wrote:
>>> 
>>> CUDA, from whatever package your system offers, and a nvidia GPU.
>>> ========================
>>> Dr Victor Lazzarini
>>> Dean of Arts, Celtic Studies and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>> 
>>>> On 3 Dec 2015, at 15:28, Menno Knevel  wrote:
>>>> 
>>>> i guess you need to install nvidia-cuda-dev as well?
>>>> What is the minimal way to get the Cuda opcodes up and running?
>>>> 
>>>> 
>>>> 
>>>> --
>>>> View this message in context:
>>>> http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745262.html
>>>> Sent from the Csound - Dev mailing list archive at Nabble.com.
>> 

Hi Victor,

i have installed the following packages in Linux Mint 64bit:
- libnvvm2
- libcublas5.5
- libcufft5.5
- libcufftw5.5
- libcursparse5.5
- libcuinj64-5.5
- libcurand5.5
- nvidia-cuda-dev
- libcuda1-340
- libcudart5.5
- libthrust-dev
- libnppc5.5
- libppi5.5
- libnpps5.5

but i'm still not able to build the cuda opcodes. I have set the cmake build
cuda option to ON.
Can you spot and tell me what package is still missing?
Do the nvidia drivers to be installed AND running for cuda to "kick in"?



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745410.html

On Ubuntu, all I need was to install cuda (i did it from the nvidia site) and set BUILD_CUDA_OPCODES to 1. What does the cmake configuration messages say?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 11 Dec 2015, at 13:41, Menno Knevel  wrote:
> 
> Hi Victor,
> 
> i have installed the following packages in Linux Mint 64bit:
> - libnvvm2
> - libcublas5.5
> - libcufft5.5
> - libcufftw5.5
> - libcursparse5.5
> - libcuinj64-5.5
> - libcurand5.5
> - nvidia-cuda-dev
> - libcuda1-340
> - libcudart5.5
> - libthrust-dev
> - libnppc5.5
> - libppi5.5
> - libnpps5.5
> 
> but i'm still not able to build the cuda opcodes. I have set the cmake build
> cuda option to ON.
> Can you spot and tell me what package is still missing?
> Do the nvidia drivers to be installed AND running for cuda to "kick in"?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745410.html

CMakeCache.txt says:

//Build the CUDA GPU opcodes
BUILD_CUDA_OPCODES:BOOL=OFF



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745414.html

but now i am downloading from https://developer.nvidia.com/cuda-downloads
1.9 GB!! WOW!!
I will try to install this .deb and see what will happen.



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745415.html

That’s not right it should be on. Use cmake .. -DBUILD_CUDA_OPCODES=1
Then see the log Cmake prints to the terminal. It will tell you either that it
set to build the cuda opcodes or not, and will report the reason.


========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 11 Dec 2015, at 14:10, Menno Knevel  wrote:
> 
> CMakeCache.txt says:
> 
> //Build the CUDA GPU opcodes
> BUILD_CUDA_OPCODES:BOOL=OFF
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745414.html

i have made it a habit to save the output of cmake as a textfile, but here
the error is printed in the terminal:

menno@muziek:~/temp$ cmake csound-develop -DBUILD_CUDA_OPCODES=1 >cmake.txt
CMake Error at /usr/share/cmake-2.8/Modules/FindCUDA.cmake:548 (message):
  Specify CUDA_TOOLKIT_ROOT_DIR
Call Stack (most recent call first):
  Opcodes/cuda/CMakeLists.txt:4 (FIND_PACKAGE)

Most of the CUDA files -not all- are copied to /var/cuda-repo-7.5-local but
i don't know how to make this clear to cmake?



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745417.html

but i don't think that /var is the right place to poin to, because i see only
.deb files there.
I'll give the list of all of the installed files of CUDA:

/.
/etc
/etc/apt
/etc/apt/sources.list.d
/etc/apt/sources.list.d/cuda-7-5-local.list
/usr
/usr/share
/usr/share/doc
/usr/share/doc/cuda-repo-ubuntu1404-7-5-local
/usr/share/doc/cuda-repo-ubuntu1404-7-5-local/changelog.Debian.gz
/usr/share/doc/cuda-repo-ubuntu1404-7-5-local/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/cuda-repo-ubuntu1404-7-5-local
/var
/var/cuda-repo-7-5-local
/var/cuda-repo-7-5-local/GPGKEY
/var/cuda-repo-7-5-local/Packages.gz
/var/cuda-repo-7-5-local/Release
/var/cuda-repo-7-5-local/Release.gpg
/var/cuda-repo-7-5-local/cuda-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-command-line-tools-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-core-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cross-aarch64-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cross-aarch64_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cross-armhf-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cross-armhf_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cross-ppc64el-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cross-ppc64el_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cublas-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cublas-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-cublas-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-cublas-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-cublas-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cudart-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cudart-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-cudart-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-cudart-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-cudart-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cudnn-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-cufft-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cufft-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-cufft-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-cufft-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-cufft-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-curand-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-curand-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-curand-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-curand-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-curand-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cusolver-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cusolver-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-cusolver-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-cusolver-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-cusolver-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cusparse-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-cusparse-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-cusparse-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-cusparse-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-cusparse-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-documentation-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-driver-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-driver-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-driver-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-driver-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-driver-headers-cross-armhf_352.39-1_armhf.deb
/var/cuda-repo-7-5-local/cuda-driver-libs-cross-armhf_352.39-1_armhf.deb
/var/cuda-repo-7-5-local/cuda-drivers_352.39-1_amd64.deb
/var/cuda-repo-7-5-local/cuda-gdb-src-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-license-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-minimal-build-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-misc-headers-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-misc-headers-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-misc-headers-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-misc-headers-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-npp-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-npp-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-npp-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-npp-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-npp-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-nvrtc-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-nvrtc-cross-aarch64-7-5_7.5-18_aarch64.deb
/var/cuda-repo-7-5-local/cuda-nvrtc-cross-armhf-7-5_7.5-18_armhf.deb
/var/cuda-repo-7-5-local/cuda-nvrtc-cross-ppc64el-7-5_7.5-18_ppc64el.deb
/var/cuda-repo-7-5-local/cuda-nvrtc-dev-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-runtime-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-samples-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-toolkit-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda-visual-tools-7-5_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/cuda_7.5-18_amd64.deb
/var/cuda-repo-7-5-local/gpu-deployment-kit_352.39-1_amd64.deb
/var/cuda-repo-7-5-local/libcuda1-352_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/libxnvctrl-dev_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/libxnvctrl0_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-352-dev_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-352-uvm_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-352_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-libopencl1-352_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-modprobe_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-opencl-icd-352_352.39-0ubuntu1_amd64.deb
/var/cuda-repo-7-5-local/nvidia-settings_352.39-0ubuntu1_amd64.deb




--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745418.html

Try setting the cuda root there and see what happens

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 11 Dec 2015, at 16:06, Menno Knevel  wrote:
> 
> i have made it a habit to save the output of cmake as a textfile, but here
> the error is printed in the terminal:
> 
> menno@muziek:~/temp$ cmake csound-develop -DBUILD_CUDA_OPCODES=1 >cmake.txt
> CMake Error at /usr/share/cmake-2.8/Modules/FindCUDA.cmake:548 (message):
>  Specify CUDA_TOOLKIT_ROOT_DIR
> Call Stack (most recent call first):
>  Opcodes/cuda/CMakeLists.txt:4 (FIND_PACKAGE)
> 
> Most of the CUDA files -not all- are copied to /var/cuda-repo-7.5-local but
> i don't know how to make this clear to cmake?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745417.html

and i found a pdf on how to install it all...which frightens me.
http://developer.download.nvidia.com/compute/cuda/7.5/Prod/docs/sidebar/CUDA_Installation_Guide_Linux.pdf

I think i will stop trying because this is getting out of control.



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745420.html

It was dead easy on Ubuntu.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 11 Dec 2015, at 16:27, Menno Knevel  wrote:
> 
> and i found a pdf on how to install it all...which frightens me.
> http://developer.download.nvidia.com/compute/cuda/7.5/Prod/docs/sidebar/CUDA_Installation_Guide_Linux.pdf
> 
> I think i will stop trying because this is getting out of control.
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745420.html

The PATH variable needs to include /usr/local/cuda-7.5/bin
The LD_LIBRARY_PATH variable needs to contain /usr/local/cuda-7.5/lib64 on a

64-bit system, and /usr/local/cuda-7.5/lib on a 32-bit system

• ‣  To change the environment variables for 64-bit operating systems:

• ‣  To change the environment variables for 32-bit operating systems:

$ export PATH=/usr/local/cuda-7.5/bin:$PATH
$ export LD_LIBRARY_PATH=/usr/local/cuda-7.5/lib64:$LD_LIBRARY_PATH

$ export PATH=/usr/local/cuda-7.5/bin:$PATH
$ export LD_LIBRARY_PATH=/usr/local/cuda-7.5/lib:$LD_LIBRARY_PATH

    

and i found a pdf on how to install it all...which frightens me.
http://developer.download.nvidia.com/compute/cuda/7.5/Prod/docs/sidebar/CUDA_Installation_Guide_Linux.pdf

I think i will stop trying because this is getting out of control.



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745420.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

nearly there...csound -z reveals:

WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop1.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop4.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop3.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)

?



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745451.html

try to set LD_LIBRARY_PATH to add the cuda libs directory.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 13 Dec 2015, at 19:47, Menno Knevel  wrote:
> 
> nearly there...csound -z reveals:
> 
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop1.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop4.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop3.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> 
> ?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745451.html

I found myself needing to copy the libcudaop-files manually from my build dir to the referred lib dir as they appear not to be properly installed by 'make install'. After that things were working, I believe. 

Regards,
Anders

> 13 dec. 2015 kl. 20:47 skrev Menno Knevel :
> 
> nearly there...csound -z reveals:
> 
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop1.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop4.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop3.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> 
> ?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745451.html

never mind, i had to do: export
LD_LIBRARY_PATH=/usr/local/cuda-7.5/lib64:$LD_LIBRARY_PATH

now i have these cuda opcodes installed:
cudaconv            cudanal             cudapconv
cudasliding         cudasynth

As it turns out, Linux Mint is NOT Ubuntu and i had to install the cuda
packages by hand. I think i will make a Wiki entry and share this
information.

thanks for your help!



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745453.html

i spoke too soon; the opcodes did build, but trying the example cudasynth.csd
reveals yet another issue:

virtual_keyboard real time MIDI plugin for Csound
0dBFS level = 32768.0
Csound version 6.07 (double samples) Dec 13 2015
libsndfile-1.0.25
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop1.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop4.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
WARNING: could not open library
'/usr/local/lib/csound/plugins64-6.0/libcudaop3.so' (libcudart.so.7.5:
cannot open shared object file: No such file or directory)
UnifiedCSD:  /home/menno/onderzoek/cuda/cudasynth.csd
Calling unified file system4
STARTING FILE
Creating options
Creating orchestra
Creating score
rtmidi: virtual_keyboard module enabled
rtaudio: JACK module enabled

error: syntax error, unexpected T_IDENT  (token "cudasynth") from file
/home/menno/onderzoek/cuda/cudasynth.csd (1)
 line 22:
>>>asig cudasynth <<<
Unexpected untyped word asig when expecting a variable
Parsing failed due to invalid input!
Stopping on parser failure
cannot compile orchestra
end of score.		   overall amps:      0.0
	   overall samples out of range:        0
1 errors in performance
Elapsed time at end of performance: real: 0.003s, CPU: 0.003s


printenv shows:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/cuda-7.5/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
and
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/cuda-7.5/lib64

am i still missing a package?



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745456.html

while i will installing from the terminal i could "save" some output of this
process. I found these lines:

-- Installing: /usr/local/lib/csound/plugins64-6.0/libcudaop1.so
-- Removed runtime path from
"/usr/local/lib/csound/plugins64-6.0/libcudaop1.so"
-- Installing: /usr/local/lib/csound/plugins64-6.0/libcudaop2.so
-- Removed runtime path from
"/usr/local/lib/csound/plugins64-6.0/libcudaop2.so"
-- Installing: /usr/local/lib/csound/plugins64-6.0/libcudaop3.so
-- Removed runtime path from
"/usr/local/lib/csound/plugins64-6.0/libcudaop3.so"
-- Installing: /usr/local/lib/csound/plugins64-6.0/libcudaop4.so
-- Removed runtime path from
"/usr/local/lib/csound/plugins64-6.0/libcudaop4.so"
-- Installing: /usr/local/lib/csound/plugins64-6.0/libcudaop5.so
-- Removed runtime path from
"/usr/local/lib/csound/plugins64-6.0/libcudaop5.so"



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745457.html

That appears still to do with your system not finding libcudart.so.7.5, and it will depend on
what methods it uses to find dynamic libs.

The other thing to see is whether any other CUDA program works. The cuda installation
will have come with samples that could be built and tested. What’s the GPU model you have?

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 14 Dec 2015, at 10:21, Menno Knevel  wrote:
> 
> i spoke too soon; the opcodes did build, but trying the example cudasynth.csd
> reveals yet another issue:
> 
> virtual_keyboard real time MIDI plugin for Csound
> 0dBFS level = 32768.0
> Csound version 6.07 (double samples) Dec 13 2015
> libsndfile-1.0.25
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop2.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop1.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop5.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop4.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> WARNING: could not open library
> '/usr/local/lib/csound/plugins64-6.0/libcudaop3.so' (libcudart.so.7.5:
> cannot open shared object file: No such file or directory)
> UnifiedCSD:  /home/menno/onderzoek/cuda/cudasynth.csd
> Calling unified file system4
> STARTING FILE
> Creating options
> Creating orchestra
> Creating score
> rtmidi: virtual_keyboard module enabled
> rtaudio: JACK module enabled
> 
> error: syntax error, unexpected T_IDENT  (token "cudasynth") from file
> /home/menno/onderzoek/cuda/cudasynth.csd (1)
> line 22:
>>>> asig cudasynth <<<
> Unexpected untyped word asig when expecting a variable
> Parsing failed due to invalid input!
> Stopping on parser failure
> cannot compile orchestra
> end of score.		   overall amps:      0.0
> 	   overall samples out of range:        0
> 1 errors in performance
> Elapsed time at end of performance: real: 0.003s, CPU: 0.003s
> 
> 
> printenv shows:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/cuda-7.5/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
> and
> LD_LIBRARY_PATH=/usr/local/lib:/usr/local/cuda-7.5/lib64
> 
> am i still missing a package?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745456.html

the only libcudart.so is a link but is linking to nothing...this link is in
/usr/local/cuda/lib64 which i added to LD_LIBRARY_PATH as well.

My card is a GeForce GT610. Since yesterday i have the nvidia drivers
installed and running. 



--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745459.html

Oh, then the cuda installation is not quite right.
I don’t think you need any display drivers by the way, as cuda does not use them.

========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 14 Dec 2015, at 12:56, Menno Knevel  wrote:
> 
> the only libcudart.so is a link but is linking to nothing...this link is in
> /usr/local/cuda/lib64 which i added to LD_LIBRARY_PATH as well.
> 
> My card is a GeForce GT610. Since yesterday i have the nvidia drivers
> installed and running. 
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745459.html

still fighting here, but getting close to the point of acceptance that it
won't work on LinuxMint, i ran the cuda.run file instead the deb:

Do you accept the previously read EULA? (accept/decline/quit): accept
You are attempting to install on an unsupported configuration. Do you wish
to continue? ((y)es/(n)o) [ default is no ]: y
Install NVIDIA Accelerated Graphics Driver for Linux-x86_64 352.39?
((y)es/(n)o/(q)uit): n
Install the CUDA 7.5 Toolkit? ((y)es/(n)o/(q)uit): y
Enter Toolkit Location [ default is /usr/local/cuda-7.5 ]: 
Do you want to install a symbolic link at /usr/local/cuda?
((y)es/(n)o/(q)uit): y
Install the CUDA 7.5 Samples? ((y)es/(n)o/(q)uit): y
Enter CUDA Samples Location [ default is /home/menno ]: 
Installing the CUDA Toolkit in /usr/local/cuda-7.5 ...
Missing recommended library: libXi.so
Missing recommended library: libXmu.so

Installing the CUDA Samples in /home/menno ...
Copying samples to /home/menno/NVIDIA_CUDA-7.5_Samples now...
Finished copying samples.

===========
= Summary =
===========

Driver:   Not Selected
Toolkit:  Installed in /usr/local/cuda-7.5
Samples:  Installed in /home/menno, but missing recommended libraries




--
View this message in context: http://csound.1045644.n5.nabble.com/Csnd-dev-cuda-opcodes-on-linux-tp5745241p5745462.html