nvcc fatal : Compiler 'cl.exe' in PATH different than the one specified with -ccbin

Accelerated Computing CUDA CUDA Setup and Installation
1

I have Windows 10 x64, installed both Cuda 9.2 and 10.0 packages, latest updates. Visual Studio 2017, latest updates applied, latest SDK.

When I try and compile my cuda file, I get this error

1>D:\msradt\VideoAR_M2\camera_server\VideoARCamerasServer_2017>“C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.0\bin\nvcc.exe” -gencode=arch=compute_35,code="sm_35,compute_35" --use-local-env -ccbin “C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe” -x cu -ID:\msradt\VideoAR_M2\camera_server\External\Ximea\API -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.0\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.0\include" -G --keep-dir x64\Debug -maxrregcount=0 --machine 64 --compile -cudart static -g -DWIN32 -DWIN64 -D_DEBUG -D_CONSOLE -D_UNICODE -DUNICODE -Xcompiler "/EHsc /Wall /nologo /Od /Fdx64\Debug\vc141.pdb /FS /Zi /RTC1 /MDd " -o x64\Debug\ColorSpace.cu.obj “D:\msradt\VideoAR_M2\camera_server\VideoARCamerasServer\Utils\ColorSpace.cu”
1>nvcc fatal : Compiler ‘cl.exe’ in PATH different than the one specified with -ccbin

when I look at cl’s path, I see this:

D:\msradt\VideoAR_M2>cl
Microsoft (R) C/C++ Optimizing Compiler Version 19.16.27025.1 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

D:\msradt\VideoAR_M2>where cl
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe

cl is same path as ccbin.

so… what gives, here? What’s the issue?

2

It needs to match what is in your windows environment PATH variable.

computer…properties…advanced system settings…Environment Variables

3

I’ve found few machines where NVCC fails to compile CUDA examples with
nvcc fatal : Compiler ‘cl.exe’ in PATH different than the one specified with -ccbin
or simply errorlevel 1

Reason was in anaconda setting
HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun

see

for explanation