Actually, C++ is *highly* sensitive to the compiler and libraries used.
At present, there is only one officially guaranteed compatible C++
library, and its not libstdc++ (its libC used with Studio.)
Using libstdc++ almost guarantees that you won't be able to link with
any other C++ libraries on the system. (And yes, you have to be very
careful to only use the same compiler for everything.
If these compatibility headaches sound like a good reason to steer away
from C++ altogether, then I'd have a hard time disagreeing with you.
- Garrett
James C. McPherson wrote:
Dennis Clarke wrote:
James wrote:
Don't use the blastwave versions of libstdc++
Why not ?
Works perfectly for me.
...
$ ./hello
Hello, world!
So what/where is the problem ?
Hi Dennis,
I wasn't aware when I sent that suggestion that Greg's build
system had several different versions of g++ installed. I
should have been more specific:
Use one consistently-installed version of g++
ie, only /usr/sfw, or /opt/csw, or ..., or ...
cheers,
James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
