Rene Engelhard wrote:
Hi,
Stephan Bergmann wrote:
<http://www.openoffice.org/issues/show_bug.cgi?id=86389> still waits for
a fix, rather urgently: On Linux, (at least Sun-built) OOo (and
derivatives, like BrOffice) brings along a (rather old) libstdc++.so.6.
It can happen that there is a later libstdc++.so.6 already installed on
the system, and that certain system libraries that OOo (indirectly)
loads depend on this later version, and thus fail to work in OOo.
Functionality that is known to be affected is the KDE Look & Feel, the
KDE configuration backend, and the KDE address book.
There appears to be no obvious, general fix for this problem. I would
Unless I miss somehing - from my POV there is. Just use the normal libstdc++6
from the system and stop shipping standard libs?
Any remotely current distro uses libstdc++6. When you build against
the old libstdc++6 from gcc 3.4.1 it will work with anything later AFAIK.
Thin ice, I fear. Our stated requirements on the runtime environment do
not require a libstdc++.so.6 to be available. I have no idea
whether/how many systems are out there that would not meet that requirement.
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).
(Except maybe on the archs you run into the s/double/long double/
change or !i386, but you don't support them anyway).
the meeting. Depending on who else would want to join --- but be warned
that this will become highly technical :) --- I will arrange the meeting
as face to face or IRC, so please drop me a line until tomorrow in case
you want to join.
I'd like to if it's possible wrt time.
OK. (As we already started a discussion here, maybe we can change from
a meeting to this mailing list, anyway...)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
