On Sat, 25 Aug 2001, Martin Husemann wrote:

> >         - The only real issue I've hit is that there seems to be
> >           a problem compiling C++. A 'hello world' program will
> >           fail at runtime with:
> > /usr/lib/libstdc++.so.4: Undefined symbol "" (reloc type = 54, symnum = 18)
> >           gcc -v reports 2.95.3. Was this toolchain used to build
> >           the snapshot? (ie: groff)
>
> Well, not sure how your "Hello world" looks, but this works for me:
>
> --8<--
> #include <iostream>
>
> int main(int,char**)
> {
>         cout << "Hello, world" << endl;
>         return 0;
> }
> -->8--
>
> And it's even linked against libstdc++:
>
> a.out:
>          -lstdc++.4 => /usr/lib/libstdc++.so.4
>          -lm.0 => /usr/lib/libm.so.0
>          -lc.12 => /usr/lib/libc.so.12
>
	That identical program fails for me. It also report (at link time)

/usr/lib/libstdc++.so: warning: reference to compatibility vfork();
include <unistd.h> for correct reference

> You did an upgrade from 1.5.1 (or 1.5.2) to current via Matt's snapshot?
> Did you remove all traces of the 1.5.1 C++ toolchain/libstdc++ before doing
> this? Maybe there is old stuff left from the hacked 1.5 toolchain that now
> breaks things.

	The 1.5X was a fresh install from the snapshot, and then a later
	untar of the second 1.5X snapshot on top :)

	What gcc version are you using?

-- 
		David/absolute		-- www.netbsd.org: No hype required --