nvidia-cuda-toolkit 6.5 transition

Tomasz Rybak tomasz.rybak at post.pl
Tue Sep 8 17:32:55 UTC 2015

Thanks for information and patches.
There is possibility to just disable building CUDAND bindings.
Would it make more sense to just have something like this in d/rules:

ifeq ($(DEB_BUILD_ARCH_CPU), i386)
	./configure.py --boost-python-libname=boost_python-py \
		--boost-thread-libname=boost_thread \
		--cuda-root=/usr --cuda-enable-gl --no-cuda-enable
	./configure.py --boost-python-libname=boost_python-py \
		--boost-thread-libname=boost_thread \
		--cuda-root=/usr --cuda-enable-gl

instead of disabling entire architecture?
I'd also like to add Debian.NEWS entry describing this change.

BTW - what's the procedure now? You upload new CUDA (6.5) to unstable
and all  packages using it should be rebuilt?
I assume that rebuilding PyCUDA will also take care of rebuilding
it against new GCC, new Boost, and will use Sphinx 1.3.

At the same time - there is new upstream release which I'd like
to package.
So if you don't mind, I can take care about PyCUDA.

Best regards.

Tomasz Rybak  GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20150908/caf0b0cc/attachment.sig>

More information about the pkg-nvidia-devel mailing list