Bug#822434: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release)

lumin cdluminate at gmail.com
Fri Jul 1 06:07:27 UTC 2016


Hi all,
(please keep me in CC list)

I'm pointing out a BIG problem introduced by stretch's GCC-6-only plan.

In brief CUDA 8.0~RC fails to work with GCC-6, this conclusion
comes from my local Caffe build log as attached. 
That is to say, after GCC-6 transition *ALL* packages depending
on cuda will get removed from stretch due to FTBFS.

I don't expect Nvidia to release CUDA 8.5 before the stretch
freeze date (Q1 2017), i.e. even a freeze-exception against
cuda might not save this situation. So all maintainers maintaining
CUDA application packages have to face this harsh condition.
Do you have any solution to this problem?

Besides, I cc'ed 2 nvidia guys with a hope that they can provide
some helpful information.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: caffe_buildlog_nvcc8_gcc6_failure.txt.gz
Type: application/gzip
Size: 2216 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160701/54d79b13/attachment.bin>
-------------- 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/20160701/54d79b13/attachment.sig>


More information about the pkg-nvidia-devel mailing list