------- Additional Comments From hp at gcc dot gnu dot org 2005-01-21 17:38 ------- Digging further, there *is* a __eprintf reference in /tmp/hptmp/obj/sparc-sun-solaris2.8/libstdc++-v3/src/.libs/libstdc++.so, the one supposedly complained about when building the test-application. Now, how did it get there? Ah, it's in debug.o, from libstdc++-v3/src/debug.cc. Apparently from the asserts there, likely from the gcc-2.95.2 installation? Perhaps we need to fixinclude away all __eprintf usage? Strange that libstdc++.so could be created but not used (linked to). Supposedly because there's another, non-hidden __eprintf somewhere?
I seem to recall a related problem discussed some time the last few months. I don't remember the resolution. Maybe it was seen on darwin? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19461
