# libnvvm-13-1 review This package ships: a) binary tool (bin/cicc) b) runtime dynamic library (lib64/libnvvm.so.4.0.0) c) header files (include/nvmm.h) d) development symlink library (lib64/libnvvm.so)
Normally such a source package would produce 3 binary packages. Something like: - libnvvm-13-1: for libnvvm.so.4.0.0 and libnvvm.so.4 (never mind the soname not matching the library package name) - libnvvm-13-1-dev: for include/nvmm.h and lib64/libnvvm.so - libnvvm-13-1-tools: for bin/cicc. But sometimes these tools would be in the -dev package, depending on what it does (I haven't run it). I understand these cuda packages are full of exceptions and quirks. But I have to ask: is it intentional that libnvvm-13-1 also ships files used only for development? Is it a build-dependency of other source packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141744 Title: [needs-packaging] cuda-13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cuda-cccl-13-1/+bug/2141744/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
