Hi Martin,

On Mon, Jul 23, 2001 at 12:52:22PM +0200, Martin Husemann wrote:
> > Currently I'm struggeling with the missing libstdc++ which seems to be
> > needed by pkgsrc/databases/postgresql-lib :-/
> 
> What's wrong with the one in /usr/lib? g++ should just find it (via some
> symlink hack). Try: cd /usr/lib; ls -l gcc-lib/sparc64-netbsd/2.95.2
> 
> Maybe it's just the pkg (or autoconf) not picking it up? I have no clue how
> this will be solved in the soon-to-be-integrated variant of the newer
> toolchain. Maybe you just need to add another symlink as libstdc++.a in 
> /usr/lib?
On sparc64 there's only a /usr/lib/libstdc++.a.2.10.0 whereas with
netbsd/sparc I have 

# libstdc++.a
# libstdc++.so -> libstdc++.so.2.0
# libstdc++.so.2 -> libstdc++.so.2.0
# libstdc++.so.2.0
# libstdc++_p.a
# libstdc++_pic.a

I tried the symlinking (libstdc++.a -> libstdc++.a.2.10.0) before and
this made the c++ check ("checking whether the C++ compiler...works")
pass but then the configure fails at

# checking for string... no
# checking for class string in <string.h>... no
# configure: error: neither <string> nor <string.h> seem to define the C++ class `string\'

I blamed the missing string class on the "slightly broken"
toolchain...there is a /usr/include/g++/string but somehow this get
not included by c++. The same pkgsrc compiles on a sparc32.

What does the "soon" in soon-to-be-integrated mean? Shell I wait for a
newer toolchain or try to find my way around?

thanks,
 Oliver

-- 
   opp@MuFFiN.Org       http://www.muffin.org/~opp/      +49-173-2313691

	     "Intel Inside" - The worlds most used warning label.