Laszlo (Laca) Peter wrote: > Given that these are c++ libs, is it acceptable to ship > duplicate copies built with g++ (/usr/sfw/bin/g++) and if > so, where should they be installed?
The problem is that there is no ABI standard for g++, so you would need to create and ship different versions of the libs for each and every release of g++ that [exists, we ship, we choose to support, pick one]. When you consider that the g++ ABI has frequently changed in patches and bugfixes for g++, this doesn't leave us with any reasonable choice - we can't do "all", tying *every* C++ app to the g++ patch release schedule doesn't scale, and if we only pick one or a couple of releases, they will tend to be not the ones customers want...) As long as someone has all the source code for libs and apps (aka gentoo), the g++ abi doesn't really matter, as it is possible to compile a consistent set of things. Once you provide precompiled g++ libs, you are tied to a specific patch level of the g++ compiler tools suite. Because of this, we have historically said no to non-studio C++ libs, unless those libs only exported "C" ABIs (via extern "C" constructs). -John
