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


User mst changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'andyrtr'                 |'andyrtr,cmc,rene'
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Oct 12 12:06:59 +0000 
2010 -------
so it seems the problem is not as severe as i thought.

see this mail on upstream dev list:
http://lists.usefulinc.com/pipermail/redland-dev/2010-October/002180.html

the problem is just that librdf.h in 1.0.11 is not self-contained.
because librdf_repository.cxx only uses the librdf interface directly,
and not the raptor or rasqal interfaces, it only includes librdf.h.
so the API incompatibility of rasqal should not be a problem.

the easiest fix for this would be to upgrade to the forthcoming
redland 1.0.12 release.
please try out the prerelease tarball linked from the mail,
if it works for you.

i'll put some distro maintainers on CC to make them aware of the problem...

now i have a question regarding the configure script:
is it possible to replace this:
   PKG_CHECK_MODULES(REDLAND, redland >= 1.0.8)
with something like:
   PKG_CHECK_MODULES(REDLAND, (redland >= 1.0.8) && (redland != 1.0.11))


---------------------------------------------------------------------
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]

Reply via email to