On Thu, 30 Aug 2007, Stefan Teleman wrote: > We could include the new RogueWave/Apache Standard C++ Library in > Solaris, with the explicit caveat that it is binary incompatible with > the existing libCstd.so.1 and that one must link either against one, or > the other, but not both.
Yes, but if I understood you correctly before, the libraries that are compiled with libCstd.so.1 will not be compatible. This in effect creates the same problem we're trying to solve, to have all the code compiled with the same libs and compiler. > The same situation exists, to a certain degree, today. One can link > against libstlport4 instead of libCstd.so.1. The consequences are > identical: applications linked against libstlport4 cannot be linked > against, and are binary incompatible with, libCstd.so.1. But if BOOST was able to compile with SunStudio, everyone could use libCstd.so.1 and be happy, no? Wouldn't this be the best situation for KDE? Yes, it would still mean that folks who have gcc apps running on Linux, may need to do some porting to Studio on Solaris/OpenSolaris, but by doing so, they create an ABI compatible world, and that is good IMO. -- Alan DuBoff - Solaris x86 IHV/OEM Group
