Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CUDA host_config error in Windows 10 installation

See original GitHub issue

Hi All

Just a quick question here because CUDA/Visual Studio never returned this error in any other cuda related build.

CUDA9, Windows 10, latest GCC, with the new updated installation guidelines, everything seems to be working until I reach the apex/PyTorch Detection part. I get this error:

c:\program files\nvidia gpu computing toolkit\cuda\v9.0\include\crt/host_config.h(133): fatal error C1189: #error: -- unsupported Microsoft Visual Studio version! Only the versions 2012, 2013, 2015 and 2017 are supported! error: command 'C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v9.0\\bin\\nvcc.exe' failed with exit status 2

I’ve looked it up elsewhere and it seems like this error has been sorted with CUDA-9, line 131: #if _MSC_VER < 1600 || _MSC_VER > 1911

What am I missing?

Issue Analytics

State:
Created 4 years ago
Comments:10

Top GitHub Comments

8reactions

erick84mmcommented, Jun 20, 2019

@qalid7 Here is the procedure I took

Steps to make it work.

Uninstalled Visual Studio 2019
Uninstalled GCC (The build does not work with GCC, because GCC is not compatible with CUDA in windows yet)
Uninstalled all versions of Visual Studio
Installed Visual Studio 2017 (install 2015 for cuda 9 or follow notes)
Deleted my conda environment
followed the maskrcnn_benchmark Windows installation instructions
No problems…

Note, if you are using cuda 9 and VS 2017 you need to install the VC++ 2017 version 15.4 v14.11 toolset (you can do this from the Visual Studio 2017 installer)

After that, you need to activate the toolset as default. you can do this by using the following command

cd “C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build” .\vcvarsall.bat x64 -vcvars_ver=“14.11”

Notice that I’m using the community edition of VS, you may need to adjust the path to match the version you are using

Additionally notice that: #if _MSC_VER < 1600 || _MSC_VER > 1911

_MSC_VER has to be between 1600 and 1911 (inclusive) and as you can see in the table all VS 2015 versions are within the range, but not all VS 2017 versions are

List of MSC_VER https://dev.to/yumetodo/list-of-mscver-and-mscfullver-8nd

1reaction

qalid7commented, Jun 20, 2019

@erick84mm by downgrading you mean? I’ve both 2015, 2017 installed. Still getting that above error!

Top Results From Across the Web

Nvidia GPU fail to run with Docker and nvidia docker ... - GitHub

Provide a detailed set of steps to reproduce the bug. 1.use the attache deployment.json and try on your GPU enable X64 cpu device...

WARNING (theano.sandbox.cuda): CUDA is installed, but ...

It seems to fix a bug in using glibc 2.23 ... apt-get-update apt-get install cuda ... the line n 115 in file \usr\local\cuda-7.5\include\host-config.h...

Tutorial: Passing through GPU to Hyper-V guest VM

My original problem: In the guest VM, my audio was out of sync when watching videos on ... You DO NOT install any...

Attach a GPU to a Linux VM in Azure Stack HCI - Microsoft Learn

This topic provides step-by-step instructions on how to install and configure an NVIDIA graphics processing unit (GPU) with Azure Stack HCI ...

GPU Transcoding (Intel QuickSync and nVidia NVENC) - Emby

I installed v3.3.1.9 on Windows 10 and it seems to be humming along fine. HEVC to x264 720p 4Mbit transcodes at 50 FPS....