Ben Walton <[email protected]> writes: > Excerpts from Maciej (Matchek) Bliziński's message of Fri Jun 22 19:45:35 > -0400 2012: > >> I wouldn't like this to go unanswered. In my opinion, this is a >> reasonable target state. I don't mean that there should be only one > > For the purposes of our project, having disjointed c++ libraries is > something that can cause us serious pain. To avoid this, > standardizing on one compiler is definitely a good choice. It would > let us avoid the /opt/csw/gxx split. If we do standardize this way > though, we would likely want to rebuild anything that is c++ and > provides a library and then all of the dependant packages. I haven't > looked at how large a set of packages this is (it may not be too bad), > but it would be a lot of work too.
Not only C++ based projects are impacted. As I mentioned in this thread, you can have similar issues with C based projects when the pkg-config files contain Sun Studio specific arguments; I suspect that there are shared objects issues also but I'm not sure yet (still exploring). -- Peter _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
