On Thu, 2006-06-08 at 11:05 -0700, Richard Fish wrote:
> There is simply no way to build libstdc++-v3 with the new compiler; it
> would break any programs that need it. Gcc likes to make incompatible
> changes in the C++ ABI from one version to the next, so building -v3
> with the new gcc would give you the old stdc++ library, but the new
> ABI, and your programs would be broken.
>
> This is one of the major reasons that gcc uses itself to build itself,
> to make sure that it's ABI is consistent.
>
scarlatti ~ $ genlop libstdc++-v3
* sys-libs/libstdc++-v3
Wed Dec 21 10:45:38 2005 >>> sys-libs/libstdc++-v3-3.3.4
Sun Mar 5 07:58:19 2006 >>> sys-libs/libstdc++-v3-3.3.6
Sat Mar 18 13:23:43 2006 >>> sys-libs/libstdc++-v3-3.3.6
Sun Apr 2 04:07:24 2006 >>> sys-libs/libstdc++-v3-3.3.6
scarlatti ~ $ equery depends libstdc++-v3
[ Searching for packages depending on libstdc++-v3... ]
sys-devel/gcc-3.4.6-r1
I definitely built libstdc++-v3 with gcc-4.1.1, but interestingly genlop
doesn't report any USE or CFLAGS for it. Hmmm.
scarlatti ~ $ genlop -i libstdc++-v3
* sys-libs/libstdc++-v3
Total builds: 4
Global build time: 59 minutes and 57 seconds.
Average merge time: 14 minutes and 59 seconds.
Info about currently installed ebuild:
* sys-libs/libstdc++-v3-3.3.6
Install date: Sun Apr 2 04:07:24 2006
Anyway, I haven't had any problems, but maybe that's because no package
I have uses libstdc++-v3.
--- Vladimir
Vladimir G. Ivanovic
Palo Alto, CA 94306
+1 650 678 8014
--
[email protected] mailing list
