Compilation problem

I have a very strange and elusive problem. I am compiling a multi-file program. When I use

Code:

---

gcc -o program.app file1.cpp file2.cpp

---

It works, but when I use this code:

Code:

---

gcc -c file1.cpp
gcc -c file2.cpp
ld -o program.app file1.o file2.o

---

I get this error:

Code:

---

ld: Undefined symbols:
___gxx_personality_v0
dyld_stub_binding_helper
__ZNSt8ios_base4InitC1Ev
__ZNSt8ios_base4InitD1Ev
__ZSt4cout<br>
__ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PK

---

It doesn't work. I've looked all over the place, but I can't find any reason that it doesn't work. Any ideas?

Try using a c++ compiler to compile c++ programs

gcc is for c
g++ is for c++

> ld -o program.app file1.o file2.o
Also use the compiler to invoke the linker. There are lots of libraries and options which need to be passed to the linker which the compiler driver knows about.

g++ -o program.app file1.o file2.o

That was my mistake. I typed gcc when I meant g++. I have been using g++. I know there is a way to divide compilation and linking in c++, because I've done it before. Saddly, I don't have any of those files left. I just can't remember what worked before.

So what's wrong with
g++ -o program.app file1.o file2.o

Sure you could type
g++ -v -o program.app file1.o file2.o
to find out all the options g++ passes to the linker, then do that yourself, but what would be the point?

Actually gcc and g++ compile programs exactly the same. The difference is in linking. They are simply drivers that use file extension to compile for the correct language. The ld failed because he lacked any of the appropriate libraries to link the program. But just use g++ for everything C++ to make your life easier.

When you are compiling 50 or 60 files, you can't say

Code:

---

g++ -o program.app file1.cpp file2.cpp file3.cpp file4.cpp file5.cpp file6.cpp...

---

I don't feel like setting up a makefile for this project, but it would be nice if I didn't have to recompile every file every time.

>When you are compiling 50 or 60 files, you can't say

If you would reread Salem's post, it's the equivalent of your:
ld -o program.app file1.o file2.o

Quote:

---

>When you are compiling 50 or 60 files, you can't say

If you would reread Salem's post, it's the equivalent of your:
ld -o program.app file1.o file2.o

---

If you would read my post, you would see that I am compiling a large number of files, and I don't want to have to re-compile every time. It would be much easier and faster to link the old object to the new ones from the changed files than to recompile everything every time.

I forgot to thank you, Salem, for the g++ -v tag. I'll be trying that and I'll see if it works.

Now I feel like an idiot. -v is obviously verbose. I've used enough *nix/BSDs that I should have known that.

It turned out that there was a whole pile of linker tags to use. For future record, here they are.

Code:

---

ld -arch ppc -dynamic -o program.app -lcrt1.o -lcrtbegin.o -L/usr/lib/gcc/darwin/3.1 -L/usr/lib/gcc/darwin -L/usr/libexec/gcc/darwin file1.o file2.o -lstdc++ -lgcc -lSystem

---

Thanks alot Salem!

> If you would read my post
Yes, many times, but you still don't get it.

You can pass ".o" files to g++ just as easily as .cpp files, and it will do the same thing.

Code:

---

# compile each source file separately
g++ -c file1.cpp
g++ -c file2.cpp
# link the whole mess together
g++ -o program.app file1.o file2.o

---

See? object files being passed to the compiler!


Not an ld to be seen, and no long magic lines which need to change every time you change your host or update your compiler.

> I don't feel like setting up a makefile for this project
Well that's just being a bone-head IMO.

You'd have thought after about three hints the light would have come on.