This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: gcc vs g++ bizarre behaviour (newbie - sorry to say)
- To: Allan Peda <allan at interport dot net>
- Subject: Re: gcc vs g++ bizarre behaviour (newbie - sorry to say)
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Sun, 29 Nov 1998 23:47:35 -0600
- cc: cygwin <gnu-win32 at cygnus dot com>
Allan Peda <allan@interport.net> writes:
>
> I am not having success invoking g++ via gcc. Rather than describe
> it... take a look:
Then don't! Here's a simple formula that works: Link C programs with
gcc; link C++ programs with c++ or g++ (which are the same thing)
to get the C++ runtime libraries automatically linked in; link f77
programs with g77.
If you want to do anything else, then you have to figure out the runtime
libraries needed for each language and provide them yourself. (Hint: C++
programs usually need -lstdc++).
> bash-2.02$ ./hellocc
> hello C++ GNUish world!
> bash-2.02$ rm ./hellocc.exe
> bash-2.02$ gcc -x "c++" hellocc.cxx -o hellocc
> C:\TEMP\cccQV0Xf.o(.text+0x2a):hellocc.cc: undefined reference to `cout'
>
> C:\TEMP\cccQV0Xf.o(.text+0x2f):hellocc.cc: undefined reference to
> `ostream::oper
> ator<<(char const *)'
The above should give you the clue needed. You misunderstand the implication
of "-x c++" option.
Nothing bizarre here. It's expected and documented behaviour.
Regards,
Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".