7
CodeTalker
128d

CUDA is a fucking bitch when it comes to configure projects

Creating my first CUDA project it yelled at me it doesn't support my current gcc version, ended up with me yelling back "OY SHUTUP" and slapping some flag for it to use clang instead — basically what it advised but I didn't listen first. Fine now.

Working on this project on another fresh environment, and now it doesn't detect anything and dumbly tries to reload my CMake project with the LATEST installed gcc when I already told it to use version 8 TWICE. First by setting up a toolchain with compilers pointing to this specific version and second by passing the -DMAKE_C_COMPILER pointing to it again. Still this stubborn piece of shit tries with latest everytime.

The most applauded solution was to use update-alternatives to make gcc point to the version I want CUDA to use. Thank you genius, but what if I don't want to use a deprecated gcc version with normal Cxx projects ?

And cherry on the top of this bullshit, I'm fixing this dumb configuration issue (can't stress enough how much I hate this shit) to be able to fix an EVEN MORE annoying issue with CUDA being a bitch AGAIN and not letting me use std functions where I'm allowed to

Fuck CUDA. Fuck CMake. Fuck C. Fuck everything

Comments
  • 0
    More like : Fuck your toolchain

    Works great with windows and visual studio.
  • 2
    Feel your pain, I remember being told over and over that I was using the wrong CUDA version and to just download the latest version. It somehow takes an entire afternoon to find out they actually meant CUDA toolkit version 10.2.
  • 0
    @gibus Your hint saved me. It's because I installed from apt directly instead of installing the latest with wget ppa and all. Now it works.
    Thanks!
Add Comment