Question

8

Can't run make - gcc: command not found

rated 0 times [ 8] [ 0] / answers: 1 / hits: 192982 / 3 Years ago, fri, june 18, 2021, 8:57:16

I'm trying to follow a tutorial to get CudaMiner working on Linux. I have PAINSTAKINGLY installed NVidia drivers, Cuda 5.0 and incidentally I'm failing on the last step when I run make:

make  all-recursive

make[1]: Entering directory `/var/progs/CudaMiner'

Making all in compat

make[2]: Entering directory `/var/progs/CudaMiner/compat'

Making all in jansson

make[3]: Entering directory `/var/progs/CudaMiner/compat/jansson'

gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../..     -g -O2 -MT dump.o -MD -MP -MF .deps/dump.Tpo -c -o dump.o dump.c

/bin/bash: gcc: command not found

make[3]: *** [dump.o] Error 127

make[3]: Leaving directory `/var/progs/CudaMiner/compat/jansson'

make[2]: *** [all-recursive] Error 1

make[2]: Leaving directory `/var/progs/CudaMiner/compat'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/var/progs/CudaMiner'

make: *** [all] Error 2

I'm pretty sure I have gcc, in fact I have multiple versions of it. I installed version 4.6 (which is what cuda requires) but it doesn't seem to find it. I'm so close!

Thanks in advance.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

aciousoun

Add To Favorites

Follow

Total Points: 178

Total Questions: 110

Total Answers: 98

Location: Lithuania

Member since Fri, Sep 4, 2020

4 Years ago

answered 3 Years ago brailloni · Accepted Answer

Do this: open a terminal and type gcc --version. Does anything come up?

Alternatively, search for the gcc executable, which should be located in /usr/bin.
Do ls /usr/bin | grep gcc. What output do you get from that command?

If you get no output from either command, then you need to find your gcc executable wherever you installed it (somewhere in /usr/share maybe?). When found, do cd /usr/bin && ln -s [ABSOLUTE PATH OF GCC].

If you got no output from the first, but output from the second, then you have serious trouble, because /usr/bin is not in your PATH. Edit the file /etc/environment and ADD the following line to the end of the document: PATH="$PATH:/usr/bin".

If you got output from the first, then there is a problem somewhere with bash not reading its own PATH. I think hell would freeze before the first works, but watch you prove me wrong and freeze hell for me. :)

Hope this helps! +1 me if it does!