Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-15 Thread Lumin
>> That means, the "build your whole application with clang-3.8" >> advise is temporary and specific to CUDA 8.0. Before uploading >> CUDA 9.0 to unstable/experimental, we can change the default >> compiler back to GCC. And backporting CUDA 9.0 to stretch >> will eliminate the compiler trouble. > >

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-15 Thread Matthias Klose
On 15.05.2017 02:06, Lumin wrote: > @doko GCC-5 may be removed from unstable when CUDA 9.0 > is uploaded. See below. [I'd like to reach gcc-5 5.5 reach snapshot.debian.org, which will be around June/July. Then we can remove it]. > (Maybe doko is already in some of these lists.) > >> The problem

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-15 Thread Lumin
@doko GCC-5 may be removed from unstable when CUDA 9.0 is uploaded. See below. (Maybe doko is already in some of these lists.) > The problem is the move of some parts of the toolchain to pie by > default, without updating the whole toolchain. Whenever not using only > gcc for building object files

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-15 Thread Samuel Thibault
Lumin, on sam. 13 mai 2017 05:59:24 +, wrote: > > This was documented in NEWS.Debian.gz. Having to use "--compiler-options > > -fPIC" was however not documented in NEW.Debian.gz, at least that should > > be done. > > Well, what do you think we can to to deal with this bug? I Cc-ed gcc, llvm a

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-12 Thread Lumin
Hi, > This was documented in NEWS.Debian.gz. Having to use "--compiler-options > -fPIC" was however not documented in NEW.Debian.gz, at least that should > be done. > > Ok, but that's still something difficult to the user to work out, while > it is needed for basically any use of nvcc. Currently N

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-07 Thread Samuel Thibault
Hello, Lumin, on dim. 07 mai 2017 02:29:46 +, wrote: > I'm not sure whether this bug should be marked as serious. Since your test > cases are mixing the default cc (GCC-6) and clang-3.8 together. Well, there is no choice about this: not doing so leads to: cc-c -o test.o test.c nvcc -c t

Re: nvidia-cuda-toolkit: nvcc needs to pass -fpie to compiler

2017-05-06 Thread Lumin
Hi Samuel, I'm not sure whether this bug should be marked as serious. Since your test cases are mixing the default cc (GCC-6) and clang-3.8 together. I reproduced the failure you reported, but there is a simpler solution to the issue as shown below. test$ CC=clang-3.8 make clang-3.8-c -o tes