My openoffice-ximian install appears to have broken at some point. It now produces the following error when I try and start it: swat@tomsk swat $ oowriter Gnome session manager detected - session management disabled /opt/Ximian-OpenOffice/program/soffice.bin: /lib/libpthread.so.0: version `GLIBC_2.3.3' not found (required by /opt/Ximian-OpenOffice/program/libsal.so.3) swat@tomsk swat $ So, I am trying to reinstall openoffice-ximian, but am getting the following error: db-3.2.9/docs/ref/upgrade.3.1/sysmem.html db-3.2.9/docs/ref/upgrade.3.1/tcl.html db-3.2.9/docs/ref/upgrade.3.1/toc.html db-3.2.9/docs/ref/upgrade.3.1/tmp.html db-3.2.9/docs/ref/upgrade.3.1/txn_check.html db-3.2.9/docs/ref/upgrade.3.2/ db-3.2.9/docs/ref/upgrade.3.2/callback.html db-3.2.9/docs/ref/upgrade.3.2/db_dump.html db-3.2.9/docs/ref/upgrade.3.2/disk.html db-3.2.9/docs/ref/upgrade.3.2/handle.html db-3.2.9/docs/ref/upgrade.3.2/incomplete.html db-3.2.9/docs/ref/upgrade.3.2/intro.html db-3.2.9/docs/ref/upgrade.3.2/mutexlock.html db-3.2.9/docs/ref/upgrade.3.2/notfound.html db-3.2.9/docs/ref/upgrade.3.2/renumber.html db-3.2.9/docs/ref/upgrade.3.2/set_flags.html db-3.2.9/docs/ref/upgrade.3.2/toc.html db-3.2.9/docs/ref/upgrade.3.2/tx_recover.html db-3.2.9/docs/ref/xa/ db-3.2.9/docs/ref/xa/config.html db-3.2.9/docs/ref/xa/faq.html db-3.2.9/docs/ref/xa/intro.html db-3.2.9/docs/sleepycat/ db-3.2.9/docs/sleepycat/legal.html db-3.2.9/docs/sleepycat/license.html db-3.2.9/docs/sleepycat/contact.html db-3.2.9/docs/utility/ db-3.2.9/docs/utility/index.html db-3.2.9/docs/utility/berkeley_db_svc.html db-3.2.9/docs/utility/db_archive.html db-3.2.9/docs/utility/db_checkpoint.html db-3.2.9/docs/utility/db_deadlock.html db-3.2.9/docs/utility/db_dump.html db-3.2.9/docs/utility/db_load.html db-3.2.9/docs/utility/db_printlog.html db-3.2.9/docs/utility/db_recover.html db-3.2.9/docs/utility/db_stat.html db-3.2.9/docs/utility/db_upgrade.html db-3.2.9/docs/utility/db_verify.html tar: Error exit delayed from previous errors dmake: Error code 2, while making './unxlngi4.pro/misc/build/so_unpacked_so_berkeleydb' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-ximian-1.1.47.3/work/oo_1.1_src/berkeleydb !!! ERROR: app-office/openoffice-ximian-1.1.47.3 failed. !!! Function src_compile, Line 457, Exitcode 1 !!! Build failed! Reproducible: Always Steps to Reproduce: 1. 2. 3.
This seems to be a problem with the newest tar, please downgrade it and try again (and even better: report if it works)
*** Bug 37749 has been marked as a duplicate of this bug. ***
The original problem appears due to a glibc downgrade ...
Hmm. Well I don't remember downgrading glibc :) Is it possible it is caused by a glibc upgrade? suka: If you meant use the slightly older ebuild... that is currently running and appears to have got further than the new one
Actually I emerged glibc-2.3.3_pre20031222 then downgraded to glibc-2.3.3_pre20031212 (because of some problems with the newer version) and then upgraded again (but the current tar was compiled afterwards). Is that what you mean azarah? If yes: What would be a proper solution? @simon: Yes, thats what I meant ;-) btw: According to http://forums.gentoo.org/viewtopic.php?t=122869 more people seem to have the problem (also with plain openoffice)
-- swat@tomsk swat $ oowriter Gnome session manager detected - session management disabled /opt/Ximian-OpenOffice/program/soffice.bin: /lib/libpthread.so.0: version `GLIBC_2.3.3' not found (required by /opt/Ximian-OpenOffice/program/libsal.so.3) swat@tomsk swat $ -- That ^^. Whatever version glibc you had, it did not have the GLIBC_2.3.3 version symbols ... Also, are you sure about tar - what the issue is, is if some component contained './' or '/./', it stipped all the dirs and extracted the files into one directory. This is not the issue from the logs, as it list the proper file structure, and not the message about stripping the leading directory. Also, the patch to -r1 enabled the '-P' option to tar, which disables the issues with other bug, and fixes it for all issues. -r0 was the build with issues ... thus if he have -r1, I cannot see that that is the problem. what happens if you do: # tar -zxf /usr/portage/distfiles/db-3.2.9.tar.gz && echo $? ? Also make sure about sufficient disk space ....
I think we have been talking about two different problems, I was just commenting about the recompilation troubles not about the breakage, sorry if i was unclear. About the tar problems: Yes I am quite sure that tar is the problem here and I am even more sure that my harddisk is not full ;-) To make myself clear: I (reproducably) encountered exactly the same problem while creating the new version of openoffice-ximian (which I maintain), downgrading to the stable version of tar solved this. I was pointed at bug #37132 by pauldv , but maybe you are right and it is not the same problem but another tar-related failure. Doing tar -zxf /usr/portage/distfiles/db-3.2.9.tar.gz && echo $? produces just a lonely 0 But I will have to point out, that openoffice provides its own db in the tarball...
Some more information about the tar problem with OpenOffice (sorry, should have provided that earlier...). A little bit earlier in the log there are a lot of errors like db-3.2.9/db_printlog/tags: Cannot change ownership to uid 100, gid 100: No such file or directory
Please try with 1.13.92-r2 of tar, which have the proper fix.
Works for me with tar-1.13.92-r2, great, thanks!
Great.
*** Bug 37650 has been marked as a duplicate of this bug. ***
