[Fwd: Re: Problems linking in libstdc++-2.90.5]

[Michael Bletzinger <michael.bletzinger@ssa.crane.navy.mil>]

-------- Original Message --------
Subject: Re: Problems linking in libstdc++-2.90.5
Date: Fri, 16 Jul 1999 00:54:54 +0000
From: Michael Bletzinger <michael.bletzinger@ssa.crane.navy.mil>
Organization: NSWC Crane
To: Benjamin Kosnik <bkoz@cygnus.com>
References:
<Pine.LNX.4.04.9907151743520.12372-100000@decepticon.cygnus.com>

Benjamin Kosnik wrote:
> 
> Michael:
> Shared libs are the default: you shouldn't have to explicitly invoke them.
> As a matter of fact, don't touch the makefiles at all, if you can help it.
> 
> You should be able to just use this:
> /opt/egcs_snap/bin/g++ -L/opt/libstdc++-2.90.5/lib/ -g testcc.cc
> 
> You may want to try to see if a static binary works with this:
> /opt/egcs_snap/bin/g++ -L/opt/libstdc++-2.90.5/lib/ -g -static testcc.cc
> 


When I run these I get the following linking error:
Undefined                       first referenced
 symbol                             in file
ostream::operator<<(ostream &(*)(ostream &))/var/tmp/ccji9Crp.o
endl(ostream &)                     /var/tmp/ccji9Crp.o
ostream::operator<<(char const *)   /var/tmp/ccji9Crp.o
ld: fatal: Symbol referencing errors. No output written to a.out
collect2: ld returned 1 exit status

I had thought that this was caused by g++ linking in the old library
after including the new libraries header files. But perhaps my linker is
misbehaving.

	Michael

-- 
First Rule of Engineering Design:
It is wiser to present an unworkable design rather
than a workable design to speed up the revision process
Phone (voice): (812)854-1101    (fax):   (812)854-3437