🚀 go-pugleaf

--
In article <1993Jan7.110644.14286@cv.ruu.nl>, bartm@cv.ruu.NL (Bart
Muyzer) writes:
|> Reading specs from /usr/local/lib/gcc-lib/hp700-hpux/2.3.3/specs
|> gcc version 2.3.3
|> /usr/local/lib/gcc-lib/hp700-hpux/2.3.3/ld -u main -a archive -o fib
|>/lib/crt0.o fib.o ../../libg++.a
|>/usr/local/lib/gcc-lib/hp700-hpux/2.3.3/libgcc.a -lc
|>/usr/local/lib/gcc-lib/hp700-hpux/2.3.3/libgcc.a
|> ld: Unsatisfied symbols:
|>    __ls__FR7ostreamd (code)
|>    __ls__FR7ostreami (code)
|>    __ls__FR7ostreamPCc (code)
|> collect: /bin/ld returned 1 exit status
|>
|>It turns out that the "Unsatisfied symbols" aren't even in the just
|>build
|>libg++.a!!????
|>
|>When I link with version 2.2 of libg++, all works well. In libg++ 2.2,
|>the
|>"Unsatisfied symbols" seem to come from the file 'iostream.o'.
|>

Try putting 'setenv LDOPTS -L /usr/local/lib' in your .cshrc. I just
expierienced
a similar linker problem when I installed gcc yesterday on a 345 w/8.0.

The hp linker doesn't look in any directories other than /lib. :(.

Hope this helps.

Adrian
----------------------------------+--------------------------------------------
adrian@cs.wm.edu          ---->>>>| Support you local programmer,
adrian@cebafi.cebaf.gov     --->>>| STOP Software Patent Abuses NOW!
Member: The League for        -->>| membership info at prep.ai.mit.edu:/pub/lpf
       Programming Freedom      ->| print "join.ps" for an application
----------------------------------+--------------------------------------------