#138449 - medarkstorm - Fri Aug 24, 2007 7:40 am
Hi Guys,
I got some problem, while trying to compile an nds sample project.
I am getting the following error message:
=======================================================
C:\devkitPro\Examples\Helloworld>make clean
make: echo: Command not found
make: *** [clean] Error 127
C:\devkitPro\Examples\Helloworld>make
make: make: Command not found
make: *** [build] Error 127
C:\devkitPro\Examples\Helloworld>pause
========================================================
Pls help me to solve the problem.
I set the path for msys, devkitpro and all....
Thankx in advance.
#138451 - truedream - Fri Aug 24, 2007 8:52 am
| medarkstorm wrote: |
Hi Guys,
I got some problem, while trying to compile an nds sample project.
I am getting the following error message:
=======================================================
C:\devkitPro\Examples\Helloworld>make clean
make: echo: Command not found
make: *** [clean] Error 127
C:\devkitPro\Examples\Helloworld>make
make: make: Command not found
make: *** [build] Error 127
C:\devkitPro\Examples\Helloworld>pause
========================================================
Pls help me to solve the problem.
I set the path for msys, devkitpro and all....
Thankx in advance. |
you need to remove one export path from the makefiles
it will append noncompatible path and then make is not found
#export PATH := $(DEVKITARM)/bin:$(PATH)
I had to comment this out
the problem depends on your PATH variable setting
#138452 - Diddl - Fri Aug 24, 2007 8:54 am
I think the path is NOT set correct. This message says it cannot found make utility.
enter SET and look into this list. search fpr PATH= and check the path to devkitpro.
#138455 - truedream - Fri Aug 24, 2007 9:05 am
| Diddl wrote: |
I think the path is NOT set correct. This message says it cannot found make utility.
enter SET and look into this list. search fpr PATH= and check the path to devkitpro. |
actully: NO
the path may be correct, but if in the PATH variable are special chars or something incompatible then all the PATH is seen as invalid.
eg you can set your PATH to include path to the tools, etc.. but if you append old PATH then the new one becomes invalid
if you dont append, then the make still fails as the make itself appends old path, and that causes the build to fail
belive me I fighted this problem on several PCs and spent lot of time understanding the real issue
#138465 - medarkstorm - Fri Aug 24, 2007 12:12 pm
the path is correct, i guess....when the path was wrong, it gave some error like "make: unknown command". so it should be something else.... im seriously stuck here....pls help me out...strange thing is, no one else faced the same problem so far...
#138467 - truedream - Fri Aug 24, 2007 12:40 pm
| medarkstorm wrote: |
| the path is correct, i guess....when the path was wrong, it gave some error like "make: unknown command". so it should be something else.... im seriously stuck here....pls help me out...strange thing is, no one else faced the same problem so far... |
sure other have the same issue
I have told you the fix already:
devkitpro\devkitarm\base_rules
#export PATH := $(DEVKITARM)/bin:$(PATH)
need coment this out!
the trailing PATH make all fail with make make not found