0

I just installed Eclipse Juno and am trying to make a simple Hello World C++ Project. I also have autoconf installed, however I get the error:

Error 127 occurred while running autoreconf.

I have already read this SO post about a similar problem, but none of the suggestions seemed to solve the problem.

How do I get rid of these errors? The project was a Hello world C++ Autotools Project if that helps.

Community
  • 1
  • 1

1 Answers1

1

possibly you have created an Autotools project. You have to create an Executable Project.

http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Fgetting_started%2Fcdt_w_basic.htm

check properties.

4pie0
  • 29,204
  • 9
  • 82
  • 118
  • What is the difference between an Autotools project and an executable project? Are there advantages of using one over the other? Also, I still get the "No rule to make target all" error even when my project explorer is empty. – user2924026 Oct 27 '13 at 18:39
  • look at Project Type. From the Project type list, expand Executable and select Hello World C++ Project. when your project explorer is empty this is not strange at all. follow this tutorial, click what has to be clicked and give here a feedback. Have you created a new project? – 4pie0 Oct 27 '13 at 18:44
  • the error is on Run command, right? so now you can at least Build the project, right? – 4pie0 Oct 27 '13 at 19:16
  • Right, there are no errors regarding the executable project itself. – user2924026 Oct 27 '13 at 19:17
  • now your problem is that you cannot Run the project. You must ensure in Properties that path to your executable binary is specified or alternatively you can run it from the command line ./path_to_executable/name_of_executable – 4pie0 Oct 27 '13 at 19:19
  • Right, so now it says that there are errors existing in the project, but I can run it and it prints out "Hello World" to the console. – user2924026 Oct 27 '13 at 19:21
  • what errors, and what it means "it says" ? please be specific if you want me to help – 4pie0 Oct 27 '13 at 19:22
  • Under the problems tab, the errors that I have already mentioned are still there. However, I am able to run the project, though I still want to know how to get rid of the errors. – user2924026 Oct 27 '13 at 19:25
  • I can also tell you that I tested this out with two projects. One uses the Mac OSX toolchain, doesn't cause any errors, but raises the "No binary found" error when run. The other uses the Cross GCC toolchain, causes errors before being run, but can actually be run. – user2924026 Oct 27 '13 at 19:29
  • Oh wait, never mind, the reason it raised the no binary found error was because it wasn't built. I assumed it automatically builded for the Mac OSX toolchain project. – user2924026 Oct 27 '13 at 19:31