[geeks] bzflag on solaris

[Brian Hechinger]

ok, built 1.7e4 on my ultra2 at work with Creator3D.  2x300Mhz CPUs, 1.5GB ram.
performanse is ABYSMAL.  with all the detail off and all the extra CPU sucking
features off, it's still completely crap.  the Creator3D can't suck that bad
can it?  with all the detail on (minus textures) bzflag is silk smooth on my
Octane.  i'm not hoping for performance like that, but i would like it to be
playable anyway.

so i though i'd drop gcc and try to build it with Sun's compiler.  it doesn't
quite build, and i don't know squat about C++ so i'm unable to fix it.  it
does seem to be something simple though maybe.  here's a clip of the error:

CC    -DSUN_OGL_NO_VERTEX_MACROS  -fast -DVERSION=10705004   -DROBOT -DINSTALL_DATA_DIR=\"/usr/local/lib/bzflag\"  -I../../include  -DNDEBUG -O   -c BzfString.cxx
"/usr/include/iso/wchar_iso.h", line 100: Error: Multiple declaration for mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/./iosfwd", line 51: Error: The name mbstate_t is ambiguous, std::mbstate_t and std::mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/./iosfwd", line 78: Error: The name mbstate_t is ambiguous, std::mbstate_t and std::mbstate_t.
"/opt/SUNWspro/SC5.0/include/CC/rw/iotraits", line 56: Error: The name mbstate_t is ambiguous, std::mbstate_t and std::mbstate_t.
4 Error(s) detected.

it picks this up a LOT from different places.  so it's something that is called
often.  anyone care to take a stab at it and see what's wrong?

then i can play at work. :)

thanks!

-brian
-- 
"Oh, shut up Buddha."  -Jesus Christ (South Park)