01/07/2009] In-Reply-To: <498C6E5A.2000804 at sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
> 3) The GCC runtime libraries are built with SONAME > set to the major > version, e.g. libstdc++.so.6.0.10 SONAME is set to > libstdc++.so.6. This > implies to me compatibility is expected as long as > the major version > matches. Even with multiple version of libraries > installed, say > libstdc++.so.6.0.x and libstdc++.so.6.0.y, programs > will get whichever > version is linked to libstdc++.so.6. And even if for some reason the compatibility was broken without gcc changing the soname, as long as we know it, it would be easy to change the soname (to libstdc++.so.6b for instance) in opensolaris. > usr/i386-pc-solaris2.11 Is this strange path necessary? Can't the subdirectories (bin and lib) go directly to /usr? > usr/lib/gcc/i386-pc-solaris2.11/4.3.2/include-fixed Do you really want to ship these as part of a gcc package? It means every time one of the packages that ships the original version of one of these headers changes, you will need to upgrade the gcc package as well. One could imagine a post-install type of script that is run for any header any package installs, and run for all headers when gcc is upgraded, but that is a pain. In linux, the list of fixed headers that is shipped is usually quite minimal and includes only system headers, not firefox, postgresql or evolution... -- This message posted from opensolaris.org
