To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104495





------- Additional comments from p...@openoffice.org Wed Jun 30 16:03:30 +0000 
2010 -------
I have provided the necessary headers and libraries in our build environment for
both linux x86_32 as well as x86_64, the CWS enabling this is kde4enable. Our
very own build machine for x86_64 is getting updated to the current glibc2.5
baseline currently, so there should be no problems in principle.

Unfortunately the installed OOo hits a problem: since our builds install their
own libstdc++ and libgcc_s the system's kde libs hit that libstdc++.so.6 when
the KDE4 plugin gets loaded. Our libstdc++ however is too old and misses a
symbol e.g. on OpenSuSE 11.2. Removing our own libstdc++ from
<office>/openoffice.org/ure/lib/ solves the problem.

However both not delivering a libstdc++/libgcc_s anymore as well as upgrading
libstdc++ would be a baseline change.

@mh: This is something I would want to leave in your capable hands. I'll change
ownership of kde4enable to you. I'll also attach a patch that would not install
libstdc++.so.6 and libgcc_s anymore relying on the system version (that seems to
be the most sensible solution for me). Either that patch would need to be added
to kde4enable or libstdc++ would need to be updated in that CWS before 
integration.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@tools.openoffice.org
For additional commands, e-mail: issues-h...@tools.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to