To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112480
User mst changed the following:
What |Old value |New value
================================================================================
CC|'hr,is,kr,md,mhu,rt,sb' |'hr,is,jl,kr,md,mhu,rt,sb'
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Thu Jul 8 10:49:30 +0000
2010 -------
status update:
it turns out that building against Solaris system libxml2 is not so easy.
Solaris 10 initially had libxml2 2.6.10.
In Solaris 10 Update 14 it was upgraded to libxml2 2.6.23.
building against libxml2 2.6.10 breaks in libxmlsec (actually in xmlsecurity,
because libxmlsec is statically linked).
libxmlsec calls the function xmlParseInNodeContext, which was added to libxml2
in 2.6.12.
this call was added in libxmlsec in this commit:
http://git.gnome.org/browse/xmlsec/commit/?id=ba1366641cb503fbcac19e04f9dc72eaded818e8
the corresponding bug:
https://bugzilla.gnome.org/show_bug.cgi?id=142358
this change went into libxsmlsec 1.2.7.
(btw, there is no libxmlsec in the system on my Solaris box)
options:
1. patch libxmlsec: replace call to xmlParseInNodeContext with a dlsym lookup.
if the symbol does not exist, fall back to previous libxmlsec code.
this would re-introduce the libxmlsec bug when OOo runs on a Solaris system
older than Update 4.
2. raise Solaris baseline to Solaris 10 Update 4.
3. continue shipping our own libxml2, but build it with versioned symbols.
that should hopefully not clash when both system and our libxml2 are loaded.
currently i'm trying option 3.
---------------------------------------------------------------------
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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
