Hi,
Another line of attack I had in mind is to ship a recent version
of libstdc++.so.6 (from GCC 4.2, say), even if we continue to
build with GCC 3.4.1. The advantages are that it is simple, we do
not need to change any code, and OOo keeps running on machines
that do not already have a listdc++.so.6 installed (see above);
the disadvantage is that it only cures the current symptoms and is
no general fix (as in the future system libraries can again have
dependencies on then more current versions of libstdc++.so.6).
Any objections against solving issue 86389 this way? (Heiner told
me that Sun Hamburg might switch to some GCC 4 for the final OOo
3.0 on Linux, anyway). If there are no objections, we could cancel
any further meetings on this...
I have an objection. The solution is nonsense. We do not want binary
libstdc++.so.6 in the CVS. If this solution sounds appropriate for
commercial software, it is no go fo OpenOffice.org.
--
Pavel Janík
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
