Bug#914804: fixed in pycuda 2018.1.1-2

Graham Inggs ginggs at debian.org
Fri Jan 11 13:09:21 GMT 2019

Control: severity -1 important

Hi Santiago

On 2019/01/11 14:54, Santiago Vila wrote:
> Hi. Sorry for the reopening but this is apparently still happening.
> The error is now slightly different:
> /usr/bin/ld: cannot find -lcuda
> collect2: error: ld returned 1 exit status
> error: command 'x86_64-linux-gnu-g++' failed with exit status 1

The error you now see has nothing to do with boost1.67.

I believe this is due to the following temporary change in 
nvidia-cuda-toolkit 9.2.148-3 [1]:

    * Relax the libcuda1 dependency to start the transition in unstable
      while the required driver is still in experimental.

I'm lowering severity since pycuda is in contrib and not autobuilt.
This bug should not block it from migrating to testing.



More information about the pkg-nvidia-devel mailing list