error in socket based application

[mazazino]

hi..
im working on a socket API application that simulates concurrent server using fork()..anyway im trying to compile it using plain old gcc compiler:

gcc concFork.cpp -o conc

and this is the error im getting:

/tmp/ccm3Et4Z.o:(.eh_frame+0x11): undefined reference to `__gxx_personality_v0'
collect2: ld returned 1 exit status

any idea what the problem might be?

[mazazino]

hello again
i tried something different..i thought the problem was one of the socket library functions but it wasnt..
i tried the following program:

#include <stdio.h>

int main()
{
	printf("print something\n");
        return 0;
}

and the same error came out...so its something that has nothing to do with the sokcet library..so any ideas?

[wje_lf]

Instead of the gcc command, try the g++ command.

[mazazino]

ya g++ worked..thanx..do u mean gcc is a C compiler and g++ is a cpp compiler?..

[wje_lf]

No. I tried your second program (the simple one) in a file with a .cpp extension using the gcc command, and the program ran without problems. The reason that I suggested using the g++ command is that I've seen people with a similar problem, and the suggestion came up to use g++, and it seemed to fix their problem (this problem that I apparently don't have).

The gcc command typically runs a compiler, an assembler, and a linking loader. It's supposed to recognize from the extension (in this case, .cpp) whether the program is, say, C or C++. Based on that, it should cause the appropriate stuff (lots of it, much of which I don't understand) to happen.

What's failing in your case is that each normal free-standing application (like your second program, the simple one) can't run with just the code you provide. There needs to be some preliminary setup before main() is called. This is previously compiled code which is installed with your C/C++ compilation stuff. There is one for C, and another for C++. My guess is that the linking loader loaded the wrong one, and failed because the proper external symbol was missing.

Again, I didn't have this problem, and it could be a problem with how the C/C++ compilation stuff is configured/installed for your system.