| Summary: | app-office/libreoffice-3.4.3.2-r1 (and 3.3.3) runtime crash: libunordfli.so: undefined symbol: librdf_new_world using build option with-system-redland | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | daid kahl <daidxor+bugz> |
| Component: | New packages | Assignee: | Gentoo Office Team <office> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
patch for 3.4.3.2-r1
lo-3.4 with the affected file |
||
|
Description
daid kahl
2011-10-31 01:51:52 UTC
Created attachment 291325 [details, diff]
patch for 3.4.3.2-r1
A quick fix to force the internal redland. Works for me.
Please note I am also usually using MAKEOPTS=-j1 for LibreOffice. That's done in my /etc/portage/env/app-office/libreoffice: #LO requires slightly less aggressive compile settings export MAKEOPTS="-j1" export FEATURES="collision-protect sandbox userpriv usersandbox buildpkg" buildpkg is enable from me wanting a good binary sticking around when I have to deal with ebuilds getting changed back to using system-redland. This does not make me happy, I really hoped I already fixed this stuff. Meh more coding for me, I will try to look to it and if it takes more time I will use the attached patch to use internal redland (TBH I would really rather fix this stuff for good :)). Also for other notes you don't need to tweak the FEATURES or jobs now on libreoffice. They should be parallel safe :) Could you give me some file which you reproduce the issue with? I am now unable to get this undefined warning from any of my builds. (In reply to comment #5) > Could you give me some file which you reproduce the issue with? > > I am now unable to get this undefined warning from any of my builds. Well, I got the error even trying to save a blank document in odt format. But you may try this one, for example: http://www.goatface.org/physix/Run_Plan_Final.odt I know that was one I tried, since a colleague was asking me for some help, and I couldn't show this file at that time. Created attachment 291515 [details]
lo-3.4 with the affected file
I am really unable to reproduce this when using libreoffice-bin-3.4.3.2-r1.
Could you try that package?
Also it looks like bug because you don't have raptor installed, try to install just raptor and see how it behaves, the raptor should be harddep for both rasqual and redland, I will bump version requirements in the ebuild to ensure fresh enough redland anyway... > I am really unable to reproduce this when using libreoffice-bin-3.4.3.2-r1.
>
> Could you try that package?
This is the package I am using. Originally saw the bug on 3.3.3 (the first time I was able to build successfully with system-redland), and it persisted to 3.4.3.2-r1 upgrade.
Will update redland, raptor, and so on, and try the build again. Gonna sneak that present binary buildpkg somewhere else though...
(In reply to comment #8) > Also it looks like bug because you don't have raptor installed, try to install > just raptor and see how it behaves, the raptor should be harddep for both > rasqual and redland, I will bump version requirements in the ebuild to ensure > fresh enough redland anyway... I updated redland as in the original post emerge pretend output, which also installed the version 2 slot of raptor, installed mhash, and updated rasqal. Changed my LO ebuild so the system-redland is used, rebuilt LO, but the problem comes back. Re-emerged the binary package I set aside using the internal redland and again I can use LO without any issues. I should also note, compared to the build error of a couple years ago, this is a new PC with a fresh install as of April 2011. So it shouldn't be any weird lurking software that's causing the problem. But the make.conf is pretty similar to the other case. Can it be some kind of USE flag issue? I really dunno what can cause this... I could recommend slight cleanup of your gentoo with removal of your definiton of LDFLAGS (we use now as-needed everywhere) and emerge -euD @world to update everything (yeah consuming i know but should solve the issue). The without --as-needed setup is quite prone for errors, specially for lo. So, did you get to reemerge your system with updated ldflags? |
