Eclipse Make Main.o Error 127
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more
Make Error 127 Ubuntu
about Stack Overflow the company Business Learn more about hiring developers or posting ads make * * * src main o error 127 with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow
Make Error 127 Linux
is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Eclipse CDT error: “make: *** [src/test2.o] Error 127” up vote 0 down make: : command not found error 127 vote favorite On Windows XP I've installed Eclipse CDT. I've installed cygwin including make, gcc, g++, and gdb. I've added C:\cygwin\bin to the windows path variable. When I create the default HelloWorld project in Eclipse and try to build, I get the following text in the console: make all make: echo: Command not found make: * [src/test3.o] Error 127 If I try make at the command line, then all's well. error 127 occurred while running autoreconf Other clues: Note that I added C:\cygwin\bin to the path rather than C:\cygwin\usr\bin because I didn't find my GNU toolchain in \usr\bin but in \bin. This seems to contradict some online documentation. Stranger still, when I type which make in the command window (not cygwin bash), it reads /usr/bin/make ! I might have installed a new version of cygwin over an old version. I noticed some warnings about this, but since nothing seemed to be wrong with cygwin once complete (and further, since make from the cygwin bash works ok), I didn't dig deeper here. (Note: there is a related question that I didn't find helpful. Perhaps it's answer was over my head.) eclipse makefile cygwin eclipse-cdt share|improve this question asked Aug 15 '10 at 2:25 JnBrymn 8,7992065108 add a comment| 6 Answers 6 active oldest votes up vote 1 down vote accepted The problem is that there is no echo binary in your PATH. Locate echo, and add it to your PATH environment variable. share|improve this answer answered Aug 15 '10 at 2:27 Borealid 51.9k87399 That's what I thought too, but: which echo --> /usr/bin/echo. Also echo $0 --> bash. Do I misunderstand something? –JnBrymn Aug 15 '10 at 2:34 @J
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies
Make Echo Command Not Found
of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a http://stackoverflow.com/questions/3485941/eclipse-cdt-error-make-src-test2-o-error-127 minute: Sign up Eclipse CDT with MinGW GCC Make Error 127 up vote 0 down vote favorite I'm currently trying to set up a dev environment and I can't get a simple "hello world" application to build properly. I have Eclipse and MinGW with GCC installed and have added C:\MinGW\bin C:\MinGW\msys\1.0\bin to my path and am using C:\MinGW\msys\1.0\bin\make.exe as the build command. http://stackoverflow.com/questions/15663388/eclipse-cdt-with-mingw-gcc-make-error-127 Whenever I try to build, I get the following error: Description Resource Path Location Type make: *** [TCP.exe] Error 127 TCP C/C++ Problem c++ c eclipse gcc mingw share|improve this question edited Mar 27 '13 at 16:03 trojanfoe 91.4k11133169 asked Mar 27 '13 at 15:58 Dyne 614 Take a look at this question. Maybe it can help. stackoverflow.com/questions/12165746/… –user995502 Mar 27 '13 at 16:03 1 if you just use make.exe (or mingw32-make.exe or whatever your executable is called) on the command line does it work? At least that can isolate an eclipse setup issue from a install/path issue –Mike Mar 27 '13 at 16:07 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote With Eclipse, MinGW integrates seamlessly. Make sure you have the following added to your environmental path: YourPath\MinGW\include; YourPath\MinGW\bin; When choosing to make a new C++ project, I personally prefer an Empty Project under Project type: and ensure that the MinGW GCC is listed under Toolchains:. Choose both of those, give the project a name, and select Finish. IF MinGW is not under Too
command Post a reply 7 posts by jstoezel » Tue Aug 13, 2013 12:21 am Hi:While trying to setup Eclipse for cross compiling in Windows 7 64, I've https://www.raspberrypi.org/forums/viewtopic.php?t=52639&p=404553 followed this tutorial to the letter:http://www.raspberry-projects.com/pi/pr ... ng-eclipseHowever when compiling I get the following error:Code: Select allarm-unknown-linux-gnueabi-g++ -IC:\jss\9-Utility\0-Cygwin\opt\cross\x-tools\arm-unknown-linux-gnueabi\arm-unknown-linux-gnueabi\sysroot\usr\include -O0 -g3 -Wall -c -fmessage-length=0 -v -MMD -MP -MF"src/HelloWorldRpi.d" -MT"src/HelloWorldRpi.d" -o "src/HelloWorldRpi.o" "../src/HelloWorldRpi.cpp"
make: *** [src/HelloWorldRpi.o] Error 127
src/subdir.mk:18: recipe for target `src/HelloWorldRpi.o' failedIt's a make error 127 which supposedly stands for unknown command, though make doesn't specify which command is unknown.Cygwin seems to know where make and error 127 arm-unknown-linux-gnueabi-g++ are:Code: Select all$ make -v
GNU Make 3.82.90
Built for x86_64-unknown-cygwin
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Code: Select all$ arm-unknown-linux-gnueabi-g++ --version
Actually what's weird is that arm-unknown-linux-gnueabi-g++ doesn't return a single thing, make error 127 even when the version is requested. Any help to get this sorted will be greatly appreciated.Jean Posts: 6Joined: Mon Jan 21, 2013 8:15 pm by jjackowski » Tue Aug 13, 2013 11:42 pm That error is usually caused by the system not finding some library that a program, gcc in this case, needs. I'm sure its giving back error 127 when you request the version, too. It might be that a required path isn't in the path environment variable. Try running it some other way, like from the Windows command prompt, or even explorer. You might get a better error. Some things will eat the error; I've seen Java do this when running commands, and I think Cygwin has the same issue.This kind of fun is why I don't run Windows at home. Posts: 44Joined: Thu Jan 10, 2013 5:25 am by jstoezel » Wed Aug 14, 2013 2:19 pm I don't think this issue is due to the system not finding gcc. As explained, I am able to invoke gcc from both cygwin and the windows prompt.When I do so, gcc does not output anything, not even its version (--version). Since then I've paid the $10 f