01-27-2012, 02:59 PM

using osx 10.6, installed xcode 3.1.2 and successfully used.
Then used Terminal, compiled very small pgm - using one cout statement. Cannot execute or find compiled pgm even by using command g++ name.cpp -o outstuff.
Compile seems to have been successful but I cannot find in any folder the output. I think that auto linking would be done - ?? Several net people said after compile - just type ./a.out to run. No workee.
Thanks for any help - loux

01-27-2012, 03:09 PM

After you compile an app, unless you've specified a binary name, you should have an "a.out" binary. What are the commands you're executing?

01-27-2012, 04:48 PM

terminal: /developer/usr/bin g++ xtest.cpp.save -o stuff
terminal: ./stuff
error mess from bash: no such file or directory

01-27-2012, 05:05 PM

Is your binary there when you do an ls? Your syntax is correct.

Mikes-iMac:foo mike$ g++ main.cpp -o foobar
Mikes-iMac:foo mike$ ls
foo.1    foobar   main.cpp
Mikes-iMac:foo mike$ foobar
-bash: foobar: command not found
Mikes-iMac:foo mike$ ./foobar
Hello, World!
Mikes-iMac:foo mike$

01-27-2012, 05:16 PM

ls lists no file that I named in the g++ xtest.cpp.save -o stuff.
It does list the file xtest.cpp.save which I created with Pico.
stuff has disappeared and the xcode compiler just threw it away!
Loux

01-27-2012, 05:18 PM

.. and you got no errors during compile, have full write permissions to the directory etc?

01-27-2012, 06:07 PM

no errors during compile. full r w permission to source code. I do not know how to give full r/w permission the usr directory but I assume I am the only user the only admin on this personal mac in my home. Fantastic communications, Mike. I never knew that the forum would help this much - only signed on today.
Loux in Colo.

01-27-2012, 10:09 PM

Try adding a -v switch, and post the output. Also you can try doing it as..

g++ xtest.cpp.save -o ~/stuff

at which point it should be in your home directory

01-27-2012, 10:35 PM

You don't need the /Developer/usr/bin/ bit - gcc should be in your path.

The command you executed is no different than what Dysfunction or I execute which creates a binary in the current working directory. It's hard to tell you what might be wrong with this since there is absolutely nothing wrong with your command. My only suggestion would be to check what Dysfunction mentioned - privileges for the current working directory. Out of what directory are you trying to compile this code?

02-03-2012, 01:52 PM

I never succeeded in compiling with g++ in terminal. I do wish to correct myself: I had xcode3.2.1 and not 3.2.2. I uninstalled 3.2.1 and downloaded xcode 3.2.2 for Apple. This version has a very nice interface for beginners. Click in new project ( in the intro ), click on Application and command line and you have a nice setup for c prog - using the good editor and build and run. Now I see no reason to mess around with terminal and g++. Just thought people would like to know. Thanks for the help I did get - Loux