Oliver Braun wrote:
Hi Stephan et al.,
Stephan Bergmann wrote:
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 am not sure I understand the plan yet:
libstdc++ is currently #ifdef'ed in scp2 with:
#if defined _gcc3 && !(defined FREEBSD || defined NETBSD \
|| defined MACOSX || defined SYSTEM_STDLIBS || defined(WNT))
Does this mean with switching to gcc4 we no longer ship libstdc++ ?
No (see cmc's response). My plan is to ship a (recent) libstdc++.so.6
with Sun Hamburg built OOo, independent of whether Sun Hamburg builds
OOo with GCC 3.4.1 (as done at the moment) or some later GCC 4 (see my
other, clarifying, response).
-Stephan
With which version of gcc do we build 64-bit linux at the moment ?
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
