Summary: | openoffice-3.0.x emerge fails on: check_libpyuno.so: undefined symbol: PyUnicodeUCS2_GetSize | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | florenzopaolo.dimagli |
Component: | New packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | serkan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
florenzopaolo.dimagli
2009-02-27 11:16:53 UTC
Can you try remerging pyxml? yes, I've tried now remerging pyxml: same result, same messages. I did another test too. I unmerged pyxml and "emerge --depclean -p" told me that it was required by javatoolkit only. so I get rid of both and tried remerging ooo: same result, same messages. Then I emerged pyxml javatoolkit and ooo, but it failed again. Now I've remerged python forcing the use flag -ucs2 both changing it into the ebuild and by command line (USE="-ucs2" emerge ...) and I'm trying to remerge ooo again. I'll keep you informed. After this attempt I guess that I've tried everything that, as a newbie, I could imagine. Two details: 1) the use flag -ucs2 in make.conf was put after the first failure, as measure of desperation. 2)at the moment there's no version of ooo installed. (In addition to comment #2) > Now I've remerged python forcing the use flag -ucs2 both changing it into the > ebuild and by command line (USE="-ucs2" emerge ...) and I'm trying to remerge > ooo again. I'll keep you informed. Same result as above. Same error message from emerge. Now what? I don't know what this module pyuno does, but I feel that I don't use it at all, so is there any way to avoid compiling it, just it? openoffice-3.0.0 has now been emerged successfully. did it after purging a misplaced installation of python, like suggested by a wise gentoo developer in relation to another bug I filed. In that config.log the path where the configure found python was /usr/local/python2.5 /usr/local/bin/python, etc. What did the trick was: 1.removing python stuff from /usr/local 2.remerging python (my initiative, maybe unnecessary) 3.emerging the failing packages (in this case openoffice-3.0.0). Of course before doing this I fixed all my exotic changes to use flags shown above. Maybe that python stuff was a manual installation for emergency recovery of portage that I did months ago, not sure. For this reason I'm proposing to mark this bug as resolved invalid. I'm going to write soon the solution on the (very few) forums where I found this apparently crazy. Thank you. |