From: j DOT aldrich6 AT genie DOT com
Message-Id: <199607192348.AA122340129@relay1.geis.com>
Date: Fri, 19 Jul 96 23:35:00 UTC 0000
To: x-aes AT telelogic DOT se
Cc: djgpp AT delorie DOT com
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Subject: Re: Getting a "unresolved symb

Reply to message 7016082    from X-AES AT TELELOG on 07/19/96  2:14AM


>| Second, you must link the C++ library when you compile.  It's called
>| 'libgpp.a', and you have to link it with the -l command, like so:
>|
>| gcc [blah] -o foo.exe foo.cc -lgpp
>
>Even if I use gxx?

If you use gxx, this is taken care of for you.

>| BTW, all this is in the FAQ (faq201b.zip), which answers zillions of the
>
>Checked it, no hints for solution.

Try reading section 8, specifically 8.7.  If none of that helps, try
reposting your problem, and mention that you didn't find the answer
in the FAQ.

Another thing that comes to mind is the possibility that 'new' is an
inlined function in C++.  There are a couple of functions that are
defined only in the header files as inline functions.  If you don't
compile with optimizations, however, then they aren't inlined and
the linker tries to look in the libraries for the functions and doesn't
find them.  Try using -O when you compile, and see if this resolves
the problem.

BTW, don't worry about optimizations vs. debugging info; gcc allows
you to do both at the same time.

John