more virtual packages for providing libcuda.so.1 and libOpenCL.so.1

Graham Inggs graham.inggs at gmail.com
Tue Jul 16 09:48:38 UTC 2013


On 16 July 2013 11:37, Andreas Beckmann <anbe at debian.org> wrote:

> Yes:
>
>    dh_shlibdeps -a
> dpkg-shlibdeps: error: couldn't find library libcuda.so.1 needed by
> debian/nvidia-profiler/usr/bin/nvprof (ELF format: 'elf64-x86-64';
> RPATH: '')
>

Thanks.  I wonder if we can override this.  My thinking is there's no
compiling or linking happening when nvidia-cuda-toolkit is built, files are
just unpacked and put in the right places, unless I missed something.


>
> > i.e. does the build system really need an Nvidia driver installed?
>
> Unless libcuda1 is split out to a separate package :-)
>

I thought about this for Ubuntu, and in the end I don't think we'd gain
much.  Because we have multiple nvidia driver versions per distribution,
we'd still end up with libcuda-304, libcuda-319, etc. and still need to
employ all the .shlibs tricks to work around that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20130716/1a4b6898/attachment-0001.html>


More information about the pkg-nvidia-devel mailing list