nvidia-cuda-toolkit 6.5 transition

[Tomasz Rybak]

Dnia 2015-09-08, wto o godzinie 20:21 +0200, Andreas Beckmann pisze:
> On 2015-09-08 19:32, Tomasz Rybak wrote:
> > 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:
> > 
> > override_dh_auto_configure:
> > 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
> > -curand
> > else
> > 	./configure.py --boost-python-libname=boost_python-py \
> > 		--boost-thread-libname=boost_thread \
> > 		--cuda-root=/usr --cuda-enable-gl
> > endif
> 
> simplified and using the correct variable:
> 
> override_dh_auto_configure:
> 	./configure.py --boost-python-libname=boost_python-py \
> 		--boost-thread-libname=boost_thread \
> 		--cuda-root=/usr --cuda-enable-gl \
> 		$(if $(filter $(DEB_HOST_ARCH),i386),--no-cuda-enable
> -curand)

Thanks. But HOST? Will it work if I build i386 package in pbuilder
on amd64?

> 
> > 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
> 
> after we got a transition slot
> 

OK. So for now I'll apply patches from this thread, test PyCUDA
with new Boost and GCC (from unstable) and CUDA 6.5
(from experimental)  and when you upload 6.5 to unstable
I'll follow with PyCUDA.

Best regards.

-- 
Tomasz Rybak  GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860
http://member.acm.org/~tomaszrybak


-------------- 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/34bee1ac/attachment.sig>