nvcc wants 0.f to be replaced with 0 or 0.0 to be replaced with 0. If the floating point constant needs the extra precision (i.e. 3.408f ) there is no complaint. I discovered this by changing NVIDIA CUDA sample code, but had to stop when system headers used offending floating-point constants.
The nvcc compiler works again if I point LD_LIBRARY_PATH to an extracted copy of 2.17-317’s libc.so.6 & libc-2.17.so, so it seems to be something in the glibc implementation.
I am a newcomer to this forum, so my apologies if I this is not directly related, but is this the cause of the problems that I have recently started seeing along the lines of