Re: Bad news to CUDA applications (was: Re: GCC 6 & binutils for the Debian stretch release)
Le 01/07/2016 à 08:51, lumin a écrit :
> Releated bug on ArchLinux:
> There are some hacks but none of them seems to be "an actual solution
> to packaging".
Personally, I would create a gcc/g++ wrapper in order to capture
the exact options passed by nvcc and to record the input file(s).
Then, I would try to see how things can be fixed manually (ie
find options to add to the real gcc call to compile successfully).
And, if nvidia does not update nvcc (and if the previous step
was successful), I would create a wrapper around nvcc that force
to call a gcc-wrapper (perhaps just redefining PATH would be enough)
that would add fix-flags to a real gcc call.
> On Fri, 2016-07-01 at 06:07 +0000, lumin wrote:
>> 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.
Vincent Danjean GPG key ID 0xD17897FA email@example.com
GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main