Thank you, Andreas. Your suggestion worked, but with a tweak: had to use
one of the architecture-specific versions of vcvars (vcvars64.bat) in my
case. Another alternative (for VS 2019) turned out to be running under
one of the VS-provided developer command prompts: they load their own
batch of environment vars.
Best,
-Dan
On 11/16/2019 12:23 AM, Andreas Kloeckner wrote:
Dan,
Please make sure the list stays cc'd for archival.
"Guralnik,Dan" <[email protected]> writes:
Andreas, I'm so sorry, should've done it myself so you have more info. Here is
what happens:
---------------------
C:\Users\danguralnik\Documents\GitHub\kodlab-uma-sims\mice\smooth>python
cuda_test.py
Traceback (most recent call last):
File "cuda_test.py", line 23, in <module>
""")
File "C:\ProgramData\Anaconda3\lib\site-packages\pycuda\compiler.py", line
291, in __init__
arch, code, cache_dir, include_dirs)
File "C:\ProgramData\Anaconda3\lib\site-packages\pycuda\compiler.py", line
254, in compile
return compile_plain(source, options, keep, nvcc, cache_dir, target)
File "C:\ProgramData\Anaconda3\lib\site-packages\pycuda\compiler.py", line
137, in compile_plain
stderr=stderr.decode("utf-8", "replace"))
pycuda.driver.CompileError: nvcc compilation of
C:\Users\DANGUR~1\AppData\Local\Temp\tmppoj82k3c\kernel.cu failed
[command: nvcc --cubin -arch sm_75 -m64
-Ic:\programdata\anaconda3\lib\site-packages\pycuda\cuda kernel.cu]
[stdout:
nvcc fatal : Cannot find compiler 'cl.exe' in PATH
]
------------------------
Is this something about environment variables?
Yes. The Visual Studio compilers also need to be on your PATH
environment variable. VS installs a batch file vcvars.bat that should
arrange for that.
Andreas
_______________________________________________
PyCUDA mailing list -- [email protected]
To unsubscribe send an email to [email protected]
